Layer 1 reference signal received power reporting for a secondary cell

ABSTRACT

A wireless device receives configuration parameters indicating resource configurations of reference signals for a layer 1 reference signal received power (RSRP) reporting of a secondary cell. A control element indicating activation of the secondary cell is received. In response to the control element, a layer 1 RSRP report is transmitted. The layer 1 RSRP report comprises: a first field indicating a reference signal of the reference signals of the secondary cell; and a second field indicating a layer 1 RSRP value of the reference signal.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation application of prior application Ser.No. 16/782,853, filed on Feb. 5, 2020, which is a continuationapplication of prior application Ser. No. 16/240,069, filed on Jan. 4,2019, which has issued as U.S. Pat. No. 10,567,145 on Feb. 18, 2020 andis based on and claims priority under 35 U.S.C. § 119(e) of a U.S.Provisional application Ser. No. 62/614,045, filed on Jan. 5, 2018, inthe U.S. Patent and Trademark Office, and of a U.S. Provisionalapplication Ser. No. 62/614,252, filed on Jan. 5, 2018, in the U.S.Patent and Trademark Office, the disclosure of each of which isincorporated by reference herein in its entirety.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Examples of several of the various embodiments of the present inventionare described herein with reference to the drawings.

FIG. 1 is a diagram depicting example sets of OFDM subcarriers as per anaspect of an embodiment of the present disclosure.

FIG. 2 is a diagram depicting an example transmission time and receptiontime for two carriers in a carrier group as per an aspect of anembodiment of the present disclosure.

FIG. 3 is a diagram depicting OFDM radio resources as per an aspect ofan embodiment of the present disclosure.

FIG. 4 is a block diagram of a base station and a wireless device as peran aspect of an embodiment of the present disclosure.

FIG. 5A, FIG. 5B, FIG. 5C and FIG. 5D are example diagrams for uplinkand downlink signal transmission as per an aspect of an embodiment ofthe present disclosure.

FIG. 6 is an example diagram for a protocol structure withmulti-connectivity as per an aspect of an embodiment of the presentdisclosure.

FIG. 7 is an example diagram for a protocol structure with CA and DC asper an aspect of an embodiment of the present disclosure.

FIG. 8 shows example TAG configurations as per an aspect of anembodiment of the present disclosure.

FIG. 9 is an example message flow in a random access process in asecondary TAG as per an aspect of an embodiment of the presentdisclosure.

FIG. 10A and FIG. 10B are example diagrams for interfaces between a 5Gcore network (e.g. NGC) and base stations (e.g. gNB and eLTE eNB) as peran aspect of an embodiment of the present disclosure.

FIG. 11A, FIG. 11B, FIG. 11C, FIG. 11D, FIG. 11E, and FIG. 11F areexample diagrams for architectures of tight interworking between 5G RAN(e.g. gNB) and LTE RAN (e.g. (e) LTE eNB) as per an aspect of anembodiment of the present disclosure.

FIG. 12A, FIG. 12B, and FIG. 12C are example diagrams for radio protocolstructures of tight interworking bearers as per an aspect of anembodiment of the present disclosure.

FIG. 13A and FIG. 13B are example diagrams for gNB deployment scenariosas per an aspect of an embodiment of the present disclosure.

FIG. 14 is an example diagram for functional split option examples ofthe centralized gNB deployment scenario as per an aspect of anembodiment of the present disclosure.

FIG. 15 is an example diagram for synchronization signal blocktransmissions as per an aspect of an embodiment of the presentdisclosure.

FIG. 16A and FIG. 16B are example diagrams of random access proceduresas per an aspect of an embodiment of the present disclosure.

FIG. 17 is an example diagram of a MAC PDU comprising a RAR as per anaspect of an embodiment of the present disclosure.

FIG. 18A, FIG. 18B and FIG. 18C are example diagrams of RAR MAC CEs asper an aspect of an embodiment of the present disclosure.

FIG. 19 is an example diagram for random access procedure whenconfigured with multiple beams as per an aspect of an embodiment of thepresent disclosure.

FIG. 20 is an example of channel state information reference signaltransmissions when configured with multiple beams as per an aspect of anembodiment of the present disclosure.

FIG. 21 is an example of channel state information reference signaltransmissions when configured with multiple beams as per an aspect of anembodiment of the present disclosure.

FIG. 22 is an example of various beam management procedures as per anaspect of an embodiment of the present disclosure.

FIG. 23A is an example diagram for downlink beam failure scenario in atransmission receiving point (TRP) as per an aspect of an embodiment ofthe present disclosure.

FIG. 23B is an example diagram for downlink beam failure scenario inmultiple TRPs as per an aspect of an embodiment of the presentdisclosure.

FIG. 24A is an example diagram for a secondary activation/deactivationmedium access control control element (MAC CE) as per an aspect of anembodiment of the present disclosure.

FIG. 24B is an example diagram for a secondary activation/deactivationMAC CE as per an aspect of an embodiment of the present disclosure.

FIG. 25A is an example diagram for timing for CSI report when activationof a secondary cell as per an aspect of an embodiment of the presentdisclosure.

FIG. 25B is an example diagram for timing for CSI report when activationof a secondary cell as per an aspect of an embodiment of the presentdisclosure.

FIG. 26 is an example diagram for downlink control information (DCI)formats as per an aspect of an embodiment of the present disclosure.

FIG. 27 is an example diagram for bandwidth part (BWP) configurations asper an aspect of an embodiment of the present disclosure.

FIG. 28 is an example diagram for BWP operation in a secondary cell asper an aspect of an embodiment of the present disclosure.

FIG. 29 is an example diagram for various CSI reporting mechanisms asper an aspect of an embodiment of the present disclosure.

FIG. 30 is an example diagram for semi-persistent CSI reportingmechanism as per an aspect of an embodiment of the present disclosure.

FIG. 31 is an example diagram for beam management of an activated SCellas per an aspect of an embodiment of the present disclosure.

FIG. 32 is an example diagram for beam management of a deactivated SCellas per an aspect of an embodiment of the present disclosure.

FIG. 33 is an example diagram for beam management and channel stateinformation report of an activated SCell as per an aspect of anembodiment of the present disclosure.

FIG. 34 is an example diagram for beam management and channel stateinformation report of an activated SCell as per an aspect of anembodiment of the present disclosure.

FIG. 35 is an example diagram for beam management and channel stateinformation report of an activated SCell as per an aspect of anembodiment of the present disclosure.

FIG. 36 is an example diagram for beam management and channel stateinformation report of an activated SCell as per an aspect of anembodiment of the present disclosure.

FIG. 37 is an example diagram for beam management and channel stateinformation report of an activated SCell as per an aspect of anembodiment of the present disclosure.

FIG. 38 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

FIG. 39 is a flow diagram of an aspect of an embodiment of the presentdisclosure.

DETAILED DESCRIPTION OF EMBODIMENTS

Example embodiments of the present invention enable operation of carrieraggregation. Embodiments of the technology disclosed herein may beemployed in the technical field of multicarrier communication systems.More particularly, the embodiments of the technology disclosed hereinmay relate to signal transmission in a multicarrier communicationsystem.

The following Acronyms are used throughout the present disclosure:

ASIC application-specific integrated circuit

BPSK binary phase shift keying

CA carrier aggregation

CC component carrier

CDMA code division multiple access

CP cyclic prefix

CPLD complex programmable logic devices

CSI channel state information

CSS common search space

CU central unit

DC dual connectivity

DCI downlink control information

DL downlink

DU distributed unit

eMBB enhanced mobile broadband

EPC evolved packet core

E-UTRAN evolved-universal terrestrial radio access network

FDD frequency division multiplexing

FPGA field programmable gate arrays

Fs-C Fs-control plane

Fs-U Fs-user plane

gNB next generation node B

HDL hardware description languages

HARQ hybrid automatic repeat request

IE information element

LTE long term evolution

MAC media access control

MCG master cell group

MeNBmaster evolved node B

MIB master information block

MME mobility management entity

mMTC massive machine type communications

NAS non-access stratum

NGC next generation core

NG CP next generation control plane core

NG-C NG-control plane

NG-U NG-user plane

NR new radio

NR MAC new radio MAC

NR PHY new radio physical

NR PDCP new radio PDCP

NR RLC new radio RLC

NR RRC new radio RRC

NS SAI network slice selection assistance information

OFDM orthogonal frequency division multiplexing

PCC primary component carrier

PCell primary cell

PDCCH physical downlink control channel

PDCP packet data convergence protocol

PDU packet data unit

PHICH physical HARQ indicator channel

PHY physical

PLMN public land mobile network

PSCell primary secondary cell

pTAG primary timing advance group

PUCCH physical uplink control channel

PUSCH physical uplink shared channel

QAM quadrature amplitude modulation

QPSK quadrature phase shift keying

RA random access

RB resource blocks

RBG resource block groups

RLC radio link control

RRC radio resource control

SCC secondary component carrier

SCell secondary cell

SCG secondary cell group

SC-OFDM single carrier-OFDM

SDU service data unit

SeNB secondary evolved node B

SIB system information block

SFN system frame number

sTAGs secondary timing advance group

S-GW serving gateway

SRB signaling radio bearer

TA timing advance

TAG timing advance group

TAI tracking area identifier

TAT time alignment timer

TB transport block

TDD time division duplexing

TDMA time division multiple access

TTI transmission time interval

UE user equipment

UL uplink

UPGW user plane gateway

URLLC ultra-reliable low-latency communications

VHDL VHSIC hardware description language

Xn-C Xn-control plane

Xn-U Xn-user plane

Xx-C Xx-control plane

Xx-U Xx-user plane

Example embodiments of the invention may be implemented using variousphysical layer modulation and transmission mechanisms. Exampletransmission mechanisms may include, but are not limited to: CDMA, OFDM,TDMA, Wavelet technologies, and/or the like. Hybrid transmissionmechanisms such as TDMA/CDMA, and OFDM/CDMA may also be employed.Various modulation schemes may be applied for signal transmission in thephysical layer. Examples of modulation schemes include, but are notlimited to: phase, amplitude, code, a combination of these, and/or thelike. An example radio transmission method may implement QAM using BPSK,QPSK, 16-QAM, 64-QAM, 256-QAM, 1024-QAM and/or the like. Physical radiotransmission may be enhanced by dynamically or semi-dynamically changingthe modulation and coding scheme depending on transmission requirementsand radio conditions.

FIG. 1 is a diagram depicting example sets of OFDM subcarriers as per anaspect of an embodiment of the present disclosure. As illustrated inthis example, arrow(s) in the diagram may depict a subcarrier in amulticarrier OFDM system. The OFDM system may use technology such asOFDM technology, DFTS-OFDM, SC-OFDM technology, or the like. Forexample, arrow 101 shows a subcarrier transmitting information symbols.FIG. 1 is for illustration purposes, and a typical multicarrier OFDMsystem may include more subcarriers in a carrier. For example, thenumber of subcarriers in a carrier may be in the range of 10 to 10,000subcarriers. FIG. 1 shows two guard bands 106 and 107 in a transmissionband. As illustrated in FIG. 1, guard band 106 is between subcarriers103 and subcarriers 104. The example set of subcarriers A 102 includessubcarriers 103 and subcarriers 104. FIG. 1 also illustrates an exampleset of subcarriers B 105. As illustrated, there is no guard band betweenany two subcarriers in the example set of subcarriers B 105. Carriers ina multicarrier OFDM communication system may be contiguous carriers,non-contiguous carriers, or a combination of both contiguous andnon-contiguous carriers.

FIG. 2 is a diagram depicting an example transmission time and receptiontime for two carriers as per an aspect of an embodiment of the presentdisclosure. A multicarrier OFDM communication system may include one ormore carriers, for example, ranging from 1 to 10 carriers. Carrier A 204and carrier B 205 may have the same or different timing structures.Although FIG. 2 shows two synchronized carriers, carrier A 204 andcarrier B 205 may or may not be synchronized with each other. Differentradio frame structures may be supported for FDD and TDD duplexmechanisms. FIG. 2 shows an example FDD frame timing. Downlink anduplink transmissions may be organized into radio frames 201. In thisexample, radio frame duration is 10 msec. Other frame durations, forexample, in the range of 1 to 100 msec may also be supported. In thisexample, each 10 ms radio frame 201 may be divided into ten equallysized subframes 202. Other subframe durations such as including 0.5msec, 1 msec, 2 msec, and 5 msec may also be supported. Subframe(s) maycomprise of two or more slots (e.g. slots 206 and 207). For the exampleof FDD, 10 subframes may be available for downlink transmission and 10subframes may be available for uplink transmissions in each 10 msinterval. Uplink and downlink transmissions may be separated in thefrequency domain. A slot may be 7 or 14 OFDM symbols for the samesubcarrier spacing of up to 60 kHz with normal CP. A slot may be 14 OFDMsymbols for the same subcarrier spacing higher than 60 kHz with normalCP. A slot may contain all downlink, all uplink, or a downlink part andan uplink part and/or alike. Slot aggregation may be supported, e.g.,data transmission may be scheduled to span one or multiple slots. In anexample, a mini-slot may start at an OFDM symbol in a subframe. Amini-slot may have a duration of one or more OFDM symbols. Slot(s) mayinclude a plurality of OFDM symbols 203. The number of OFDM symbols 203in a slot 206 may depend on the cyclic prefix length and subcarrierspacing.

FIG. 3 is a diagram depicting OFDM radio resources as per an aspect ofan embodiment of the present disclosure. The resource grid structure intime 304 and frequency 305 is illustrated in FIG. 3. The quantity ofdownlink subcarriers or RBs may depend, at least in part, on thedownlink transmission bandwidth 306 configured in the cell. The smallestradio resource unit may be called a resource element (e.g. 301).Resource elements may be grouped into resource blocks (e.g. 302).Resource blocks may be grouped into larger radio resources calledResource Block Groups (RBG) (e.g. 303). The transmitted signal in slot206 may be described by one or several resource grids of a plurality ofsubcarriers and a plurality of OFDM symbols. Resource blocks may be usedto describe the mapping of certain physical channels to resourceelements. Other pre-defined groupings of physical resource elements maybe implemented in the system depending on the radio technology. Forexample, 24 subcarriers may be grouped as a radio block for a durationof 5 msec. In an illustrative example, a resource block may correspondto one slot in the time domain and 180 kHz in the frequency domain (for15 KHz subcarrier bandwidth and 12 subcarriers).

In an example embodiment, multiple numerologies may be supported. In anexample, a numerology may be derived by scaling a basic subcarrierspacing by an integer N. In an example, scalable numerology may allow atleast from 15 kHz to 480 kHz subcarrier spacing. The numerology with 15kHz and scaled numerology with different subcarrier spacing with thesame CP overhead may align at a symbol boundary every 1 ms in a NRcarrier.

FIG. 5A, FIG. 5B, FIG. 5C and FIG. 5D are example diagrams for uplinkand downlink signal transmission as per an aspect of an embodiment ofthe present disclosure. FIG. 5A shows an example uplink physicalchannel. The baseband signal representing the physical uplink sharedchannel may perform the following processes. These functions areillustrated as examples and it is anticipated that other mechanisms maybe implemented in various embodiments. The functions may comprisescrambling, modulation of scrambled bits to generate complex-valuedsymbols, mapping of the complex-valued modulation symbols onto one orseveral transmission layers, transform precoding to generatecomplex-valued symbols, precoding of the complex-valued symbols, mappingof precoded complex-valued symbols to resource elements, generation ofcomplex-valued time-domain DFTS-OFDM/SC-FDMA signal for an antenna port,and/or the like.

Example modulation and up-conversion to the carrier frequency of thecomplex-valued DFTS-OFDM/SC-FDMA baseband signal for an antenna portand/or the complex-valued PRACH baseband signal is shown in FIG. 5B.Filtering may be employed prior to transmission.

An example structure for Downlink Transmissions is shown in FIG. 5C. Thebaseband signal representing a downlink physical channel may perform thefollowing processes. These functions are illustrated as examples and itis anticipated that other mechanisms may be implemented in variousembodiments. The functions include scrambling of coded bits in codewordsto be transmitted on a physical channel; modulation of scrambled bits togenerate complex-valued modulation symbols; mapping of thecomplex-valued modulation symbols onto one or several transmissionlayers; precoding of the complex-valued modulation symbols on a layerfor transmission on the antenna ports; mapping of complex-valuedmodulation symbols for an antenna port to resource elements; generationof complex-valued time-domain OFDM signal for an antenna port, and/orthe like.

Example modulation and up-conversion to the carrier frequency of thecomplex-valued OFDM baseband signal for an antenna port is shown in FIG.5D. Filtering may be employed prior to transmission.

FIG. 4 is an example block diagram of a base station 401 and a wirelessdevice 406, as per an aspect of an embodiment of the present disclosure.A communication network 400 may include at least one base station 401and at least one wireless device 406. The base station 401 may includeat least one communication interface 402, at least one processor 403,and at least one set of program code instructions 405 stored innon-transitory memory 404 and executable by the at least one processor403. The wireless device 406 may include at least one communicationinterface 407, at least one processor 408, and at least one set ofprogram code instructions 410 stored in non-transitory memory 409 andexecutable by the at least one processor 408. Communication interface402 in base station 401 may be configured to engage in communicationwith communication interface 407 in wireless device 406 via acommunication path that includes at least one wireless link 411.Wireless link 411 may be a bi-directional link. Communication interface407 in wireless device 406 may also be configured to engage in acommunication with communication interface 402 in base station 401. Basestation 401 and wireless device 406 may be configured to send andreceive data over wireless link 411 using multiple frequency carriers.According to some of the various aspects of embodiments, transceiver(s)may be employed. A transceiver is a device that includes both atransmitter and receiver. Transceivers may be employed in devices suchas wireless devices, base stations, relay nodes, and/or the like.Example embodiments for radio technology implemented in communicationinterface 402, 407 and wireless link 411 are illustrated are FIG. 1,FIG. 2, FIG. 3, FIG. 5, and associated text.

An interface may be a hardware interface, a firmware interface, asoftware interface, and/or a combination thereof. The hardware interfacemay include connectors, wires, electronic devices such as drivers,amplifiers, and/or the like. A software interface may include codestored in a memory device to implement protocol(s), protocol layers,communication drivers, device drivers, combinations thereof, and/or thelike. A firmware interface may include a combination of embeddedhardware and code stored in and/or in communication with a memory deviceto implement connections, electronic device operations, protocol(s),protocol layers, communication drivers, device drivers, hardwareoperations, combinations thereof, and/or the like.

The term configured may relate to the capacity of a device whether thedevice is in an operational or non-operational state. Configured mayalso refer to specific settings in a device that effect the operationalcharacteristics of the device whether the device is in an operational ornon-operational state. In other words, the hardware, software, firmware,registers, memory values, and/or the like may be “configured” within adevice, whether the device is in an operational or nonoperational state,to provide the device with specific characteristics. Terms such as “acontrol message to cause in a device” may mean that a control messagehas parameters that may be used to configure specific characteristics inthe device, whether the device is in an operational or non-operationalstate.

According to some of the various aspects of embodiments, a 5G networkmay include a multitude of base stations, providing a user plane NRPDCP/NR RLC/NR MAC/NR PHY and control plane (NR RRC) protocolterminations towards the wireless device. The base station(s) may beinterconnected with other base station(s) (e.g. employing an Xninterface). The base stations may also be connected employing, forexample, an NG interface to an NGC. FIG. 10A and FIG. 10B are examplediagrams for interfaces between a 5G core network (e.g. NGC) and basestations (e.g. gNB and eLTE eNB) as per an aspect of an embodiment ofthe present disclosure. For example, the base stations may beinterconnected to the NGC control plane (e.g. NG CP) employing the NG-Cinterface and to the NGC user plane (e.g. UPGW) employing the NG-Uinterface. The NG interface may support a many-to-many relation between5G core networks and base stations.

A base station may include many sectors for example: 1, 2, 3, 4, or 6sectors. A base station may include many cells, for example, rangingfrom 1 to 50 cells or more. A cell may be categorized, for example, as aprimary cell or secondary cell. At RRC connectionestablishment/re-establishment/handover, one serving cell may providethe NAS (non-access stratum) mobility information (e.g. TAI), and at RRCconnection re-establishment/handover, one serving cell may provide thesecurity input. This cell may be referred to as the Primary Cell(PCell). In the downlink, the carrier corresponding to the PCell may bethe Downlink Primary Component Carrier (DL PCC), while in the uplink, itmay be the Uplink Primary Component Carrier (UL PCC). Depending onwireless device capabilities, Secondary Cells (SCells) may be configuredto form together with the PCell a set of serving cells. In the downlink,the carrier corresponding to an SCell may be a Downlink SecondaryComponent Carrier (DL SCC), while in the uplink, it may be an UplinkSecondary Component Carrier (UL SCC). An SCell may or may not have anuplink carrier.

A cell, comprising a downlink carrier and optionally an uplink carrier,may be assigned a physical cell ID and a cell index. A carrier (downlinkor uplink) may belong to only one cell. The cell ID or Cell index mayalso identify the downlink carrier or uplink carrier of the cell(depending on the context it is used). In the specification, cell ID maybe equally referred to a carrier ID, and cell index may be referred tocarrier index. In implementation, the physical cell ID or cell index maybe assigned to a cell. A cell ID may be determined using asynchronization signal transmitted on a downlink carrier. A cell indexmay be determined using RRC messages. For example, when thespecification refers to a first physical cell ID for a first downlinkcarrier, the specification may mean the first physical cell ID is for acell comprising the first downlink carrier. The same concept may applyto, for example, carrier activation. When the specification indicatesthat a first carrier is activated, the specification may equally meanthat the cell comprising the first carrier is activated.

Embodiments may be configured to operate as needed. The disclosedmechanism may be performed when certain criteria are met, for example,in a wireless device, a base station, a radio environment, a network, acombination of the above, and/or the like. Example criteria may bebased, at least in part, on for example, traffic load, initial systemset up, packet sizes, traffic characteristics, a combination of theabove, and/or the like. When the one or more criteria are met, variousexample embodiments may be applied. Therefore, it may be possible toimplement example embodiments that selectively implement disclosedprotocols.

A base station may communicate with a mix of wireless devices. Wirelessdevices may support multiple technologies, and/or multiple releases ofthe same technology. Wireless devices may have some specificcapability(ies) depending on its wireless device category and/orcapability(ies). A base station may comprise multiple sectors. When thisdisclosure refers to a base station communicating with a plurality ofwireless devices, this disclosure may refer to a subset of the totalwireless devices in a coverage area. This disclosure may refer to, forexample, a plurality of wireless devices of a given LTE or 5G releasewith a given capability and in a given sector of the base station. Theplurality of wireless devices in this disclosure may refer to a selectedplurality of wireless devices, and/or a subset of total wireless devicesin a coverage area which perform according to disclosed methods, and/orthe like. There may be a plurality of wireless devices in a coveragearea that may not comply with the disclosed methods, for example,because those wireless devices perform based on older releases of LTE or5G technology.

FIG. 6 and FIG. 7 are example diagrams for protocol structure with CAand multi-connectivity as per an aspect of an embodiment of the presentdisclosure. NR may support multi-connectivity operation whereby amultiple RX/TX UE in RRC CONNECTED may be configured to utilize radioresources provided by multiple schedulers located in multiple gNBsconnected via a non-ideal or ideal backhaul over the Xn interface. gNBsinvolved in multi-connectivity for a certain UE may assume two differentroles: a gNB may either act as a master gNB or as a secondary gNB. Inmulti-connectivity, a UE may be connected to one master gNB and one ormore secondary gNBs. FIG. 7 illustrates one example structure for the UEside MAC entities when a Master Cell Group (MCG) and a Secondary CellGroup (SCG) are configured, and it may not restrict implementation.Media Broadcast Multicast Service (MBMS) reception is not shown in thisfigure for simplicity.

In multi-connectivity, the radio protocol architecture that a particularbearer uses may depend on how the bearer is setup. Three examples ofbearers, including, an MCG bearer, an SCG bearer and a split bearer asshown in FIG. 6. NR RRC may be located in master gNB and SRBs may beconfigured as an MCG bearer type and may use the radio resources of themaster gNB. Multi-connectivity may also be described as having at leastone bearer configured to use radio resources provided by the secondarygNB. Multi-connectivity may or may not be configured/implemented inexample embodiments of the disclosure.

In the case of multi-connectivity, the UE may be configured withmultiple NR MAC entities: one NR MAC entity for master gNB, and other NRMAC entities for secondary gNBs. In multi-connectivity, the configuredset of serving cells for a UE may comprise of two subsets: the MasterCell Group (MCG) containing the serving cells of the master gNB, and theSecondary Cell Groups (SCGs) containing the serving cells of thesecondary gNBs. For a SCG, one or more of the following may be applied:at least one cell in the SCG has a configured UL CC and one of them,named PSCell (or PCell of SCG, or sometimes called PCell), is configuredwith PUCCH resources; when the SCG is configured, there may be at leastone SCG bearer or one Split bearer; upon detection of a physical layerproblem or a random access problem on a PSCell, or the maximum number ofNR RLC retransmissions has been reached associated with the SCG, or upondetection of an access problem on a PSCell during a SCG addition or aSCG change: a RRC connection re-establishment procedure may not betriggered, UL transmissions towards cells of the SCG are stopped, amaster gNB may be informed by the UE of a SCG failure type, for splitbearer, the DL data transfer over the master gNB is maintained; the NRRLC AM bearer may be configured for the split bearer; like PCell, PSCellmay not be de-activated; PSCell may be changed with a SCG change (e.g.with security key change and a RACH procedure); and/or a direct bearertype change between a Split bearer and a SCG bearer or simultaneousconfiguration of a SCG and a Split bearer may or may not supported.

With respect to the interaction between a master gNB and secondary gNBsfor multi-connectivity, one or more of the following principles may beapplied: the master gNB may maintain the RRM measurement configurationof the UE and may, (e.g., based on received measurement reports ortraffic conditions or bearer types), decide to ask a secondary gNB toprovide additional resources (serving cells) for a UE; upon receiving arequest from the master gNB, a secondary gNB may create a container thatmay result in the configuration of additional serving cells for the UE(or decide that it has no resource available to do so); for UEcapability coordination, the master gNB may provide (part of) the ASconfiguration and the UE capabilities to the secondary gNB; the mastergNB and the secondary gNB may exchange information about a UEconfiguration by employing of NR RRC containers (inter-node messages)carried in Xn messages; the secondary gNB may initiate a reconfigurationof its existing serving cells (e.g., PUCCH towards the secondary gNB);the secondary gNB may decide which cell is the PSCell within the SCG;the master gNB may or may not change the content of the NR RRCconfiguration provided by the secondary gNB; in the case of a SCGaddition and a SCG S Cell addition, the master gNB may provide thelatest measurement results for the SCG cell(s); both a master gNB andsecondary gNBs may know the SFN and subframe offset of each other byOAM, (e.g., for the purpose of DRX alignment and identification of ameasurement gap). In an example, when adding a new SCG SCell, dedicatedNR RRC signaling may be used for sending required system information ofthe cell as for CA, except for the SFN acquired from a MIB of the PSCellof a SCG.

In an example, serving cells may be grouped in a TA group (TAG). Servingcells in one TAG may use the same timing reference. For a given TAG,user equipment (UE) may use at least one downlink carrier as a timingreference. For a given TAG, a UE may synchronize uplink subframe andframe transmission timing of uplink carriers belonging to the same TAG.In an example, serving cells having an uplink to which the same TAapplies may correspond to serving cells hosted by the same receiver. AUE supporting multiple TAs may support two or more TA groups. One TAgroup may contain the PCell and may be called a primary TAG (pTAG). In amultiple TAG configuration, at least one TA group may not contain thePCell and may be called a secondary TAG (sTAG). In an example, carrierswithin the same TA group may use the same TA value and/or the sametiming reference. When DC is configured, cells belonging to a cell group(MCG or SCG) may be grouped into multiple TAGs including a pTAG and oneor more sTAGs.

FIG. 8 shows example TAG configurations as per an aspect of anembodiment of the present disclosure. In Example 1, pTAG comprisesPCell, and an sTAG comprises SCell1. In Example 2, a pTAG comprises aPCell and SCell1, and an sTAG comprises SCell2 and SCell3. In Example 3,pTAG comprises PCell and SCell1, and an sTAG1 includes SCell2 andSCell3, and sTAG2 comprises SCell4. Up to four TAGs may be supported ina cell group (MCG or SCG) and other example TAG configurations may alsobe provided. In various examples in this disclosure, example mechanismsare described for a pTAG and an sTAG. Some of the example mechanisms maybe applied to configurations with multiple sTAGs.

In an example, an eNB may initiate an RA procedure via a PDCCH order foran activated SCell. This PDCCH order may be sent on a scheduling cell ofthis SCell. When cross carrier scheduling is configured for a cell, thescheduling cell may be different than the cell that is employed forpreamble transmission, and the PDCCH order may include an SCell index.At least a non-contention based RA procedure may be supported forSCell(s) assigned to sTAG(s).

FIG. 9 is an example message flow in a random access process in asecondary TAG as per an aspect of an embodiment of the presentdisclosure. An eNB transmits an activation command 900 to activate anSCell. A preamble 902 (Msg1) may be sent by a UE in response to a PDCCHorder 901 on an SCell belonging to an sTAG. In an example embodiment,preamble transmission for SCells may be controlled by the network usingPDCCH format 1A. Msg2 message 903 (RAR: random access response) inresponse to the preamble transmission on the SCell may be addressed toRA-RNTI in a PCell common search space (CSS). Uplink packets 904 may betransmitted on the SCell in which the preamble was transmitted.

According to some of the various aspects of embodiments, initial timingalignment may be achieved through a random access procedure. This mayinvolve a UE transmitting a random access preamble and an eNB respondingwith an initial TA command NTA (amount of timing advance) within arandom access response window. The start of the random access preamblemay be aligned with the start of a corresponding uplink subframe at theUE assuming NTA=0. The eNB may estimate the uplink timing from therandom access preamble transmitted by the UE. The TA command may bederived by the eNB based on the estimation of the difference between thedesired UL timing and the actual UL timing. The UE may determine theinitial uplink transmission timing relative to the correspondingdownlink of the sTAG on which the preamble is transmitted.

The mapping of a serving cell to a TAG may be configured by a servingeNB with RRC signaling. The mechanism for TAG configuration andreconfiguration may be based on RRC signaling. According to some of thevarious aspects of embodiments, when an eNB performs an SCell additionconfiguration, the related TAG configuration may be configured for theSCell. In an example embodiment, an eNB may modify the TAG configurationof an S Cell by removing (releasing) the SCell and adding (configuring)a new SCell (with the same physical cell ID and frequency) with anupdated TAG ID. The new SCell with the updated TAG ID may initially beinactive subsequent to being assigned the updated TAG ID. The eNB mayactivate the updated new SCell and start scheduling packets on theactivated SCell. In an example implementation, it may not be possible tochange the TAG associated with an SCell, but rather, the SCell may needto be removed and a new SCell may need to be added with another TAG. Forexample, if there is a need to move an SCell from an sTAG to a pTAG, atleast one RRC message, for example, at least one RRC reconfigurationmessage, may be send to the UE to reconfigure TAG configurations byreleasing the SCell and then configuring the SCell as a part of the pTAG(when an SCell is added/configured without a TAG index, the SCell may beexplicitly assigned to the pTAG). The PCell may not change its TA groupand may be a member of the pTAG.

The purpose of an RRC connection reconfiguration procedure may be tomodify an RRC connection, (e.g. to establish, modify and/or release RBs,to perform handover, to setup, modify, and/or release measurements, toadd, modify, and/or release SCells). If the received RRC ConnectionReconfiguration message includes the sCellToReleaseList, the UE mayperform an SCell release. If the received RRC Connection Reconfigurationmessage includes the sCellToAddModList, the UE may perform SCelladditions or modification.

In LTE Release-10 and Release-11 CA, a PUCCH is only transmitted on thePCell (PSCell) to an eNB. In LTE-Release 12 and earlier, a UE maytransmit PUCCH information on one cell (PCell or PSCell) to a given eNB.

As the number of CA capable UEs and also the number of aggregatedcarriers increase, the number of PUCCHs and also the PUCCH payload sizemay increase. Accommodating the PUCCH transmissions on the PCell maylead to a high PUCCH load on the PCell. A PUCCH on an SCell may beintroduced to offload the PUCCH resource from the PCell. More than onePUCCH may be configured for example, a PUCCH on a PCell and anotherPUCCH on an SCell. In the example embodiments, one, two or more cellsmay be configured with PUCCH resources for transmitting CSI/ACK/NACK toa base station. Cells may be grouped into multiple PUCCH groups, and oneor more cell within a group may be configured with a PUCCH. In anexample configuration, one SCell may belong to one PUCCH group. SCellswith a configured PUCCH transmitted to a base station may be called aPUCCH SCell, and a cell group with a common PUCCH resource transmittedto the same base station may be called a PUCCH group.

In an example embodiment, a MAC entity may have a configurable timertimeAlignmentTimer per TAG. The timeAlignmentTimer may be used tocontrol how long the MAC entity considers the Serving Cells belonging tothe associated TAG to be uplink time aligned. The MAC entity may, when aTiming Advance Command MAC control element is received, apply the TimingAdvance Command for the indicated TAG; start or restart thetimeAlignmentTimer associated with the indicated TAG. The MAC entitymay, when a Timing Advance Command is received in a Random AccessResponse message for a serving cell belonging to a TAG and/or if theRandom Access Preamble was not selected by the MAC entity, apply theTiming Advance Command for this TAG and start or restart thetimeAlignmentTimer associated with this TAG. Otherwise, if thetimeAlignmentTimer associated with this TAG is not running, the TimingAdvance Command for this TAG may be applied and the timeAlignmentTimerassociated with this TAG started. When the contention resolution isconsidered not successful, a timeAlignmentTimer associated with this TAGmay be stopped. Otherwise, the MAC entity may ignore the received TimingAdvance Command.

In example embodiments, a timer is running once it is started, until itis stopped or until it expires; otherwise it may not be running A timercan be started if it is not running or restarted if it is running. Forexample, a timer may be started or restarted from its initial value.

Example embodiments of the disclosure may enable operation ofmulti-carrier communications. Other example embodiments may comprise anon-transitory tangible computer readable media comprising instructionsexecutable by one or more processors to cause operation of multi-carriercommunications. Yet other example embodiments may comprise an article ofmanufacture that comprises a non-transitory tangible computer readablemachine-accessible medium having instructions encoded thereon forenabling programmable hardware to cause a device (e.g. wirelesscommunicator, UE, base station, etc.) to enable operation ofmulti-carrier communications. The device may include processors, memory,interfaces, and/or the like. Other example embodiments may comprisecommunication networks comprising devices such as base stations,wireless devices (or user equipment: UE), servers, switches, antennas,and/or the like.

FIG. 11A, FIG. 11B, FIG. 11C, FIG. 11D, FIG. 11E, and FIG. 11F areexample diagrams for architectures of tight interworking between 5G RANand LTE RAN as per an aspect of an embodiment of the present disclosure.The tight interworking may enable a multiple RX/TX UE in RRC CONNECTEDto be configured to utilize radio resources provided by two schedulerslocated in two base stations (e.g. (e) LTE eNB and gNB) connected via anon-ideal or ideal backhaul over the Xx interface between LTE eNB andgNB or the Xn interface between eLTE eNB and gNB. Base stations involvedin tight interworking for a certain UE may assume two different roles: abase station may either act as a master base station or as a secondarybase station. In tight interworking, a UE may be connected to one masterbase station and one secondary base station. Mechanisms implemented intight interworking may be extended to cover more than two base stations.

In FIG. 11A and FIG. 11B, a master base station may be an LTE eNB, whichmay be connected to EPC nodes (e.g. to an MME via the S1-C interface andto an S-GW via the S1-U interface), and a secondary base station may bea gNB, which may be a non-standalone node having a control planeconnection via an Xx-C interface to an LTE eNB. In the tightinterworking architecture of FIG. 11A, a user plane for a gNB may beconnected to an S-GW through an LTE eNB via an Xx-U interface betweenLTE eNB and gNB and an S1-U interface between LTE eNB and S-GW. In thearchitecture of FIG. 11B, a user plane for a gNB may be connecteddirectly to an S-GW via an S1-U interface between gNB and S-GW.

In FIG. 11C and FIG. 11D, a master base station may be a gNB, which maybe connected to NGC nodes (e.g. to a control plane core node via theNG-C interface and to a user plane core node via the NG-U interface),and a secondary base station may be an eLTE eNB, which may be anon-standalone node having a control plane connection via an Xn-Cinterface to a gNB. In the tight interworking architecture of FIG. 11C,a user plane for an eLTE eNB may be connected to a user plane core nodethrough a gNB via an Xn-U interface between eLTE eNB and gNB and an NG-Uinterface between gNB and user plane core node. In the architecture ofFIG. 11D, a user plane for an eLTE eNB may be connected directly to auser plane core node via an NG-U interface between eLTE eNB and userplane core node.

In FIG. 11E and FIG. 11F, a master base station may be an eLTE eNB,which may be connected to NGC nodes (e.g. to a control plane core nodevia the NG-C interface and to a user plane core node via the NG-Uinterface), and a secondary base station may be a gNB, which may be anon-standalone node having a control plane connection via an Xn-Cinterface to an eLTE eNB. In the tight interworking architecture of FIG.11E, a user plane for a gNB may be connected to a user plane core nodethrough an eLTE eNB via an Xn-U interface between eLTE eNB and gNB andan NG-U interface between eLTE eNB and user plane core node. In thearchitecture of FIG. 11F, a user plane for a gNB may be connecteddirectly to a user plane core node via an NG-U interface between gNB anduser plane core node.

FIG. 12A, FIG. 12B, and FIG. 12C are example diagrams for radio protocolstructures of tight interworking bearers as per an aspect of anembodiment of the present disclosure. In FIG. 12A, an LTE eNB may be amaster base station, and a gNB may be a secondary base station. In FIG.12B, a gNB may be a master base station, and an eLTE eNB may be asecondary base station. In FIG. 12C, an eLTE eNB may be a master basestation, and a gNB may be a secondary base station. In 5G network, theradio protocol architecture that a particular bearer uses may depend onhow the bearer is setup. Three example bearers including an MCG bearer,an SCG bearer, and a split bearer as shown in FIG. 12A, FIG. 12B, andFIG. 12C. NR RRC may be located in master base station, and SRBs may beconfigured as an MCG bearer type and may use the radio resources of themaster base station. Tight interworking may also be described as havingat least one bearer configured to use radio resources provided by thesecondary base station. Tight interworking may or may not beconfigured/implemented in example embodiments of the disclosure.

In the case of tight interworking, the UE may be configured with two MACentities: one MAC entity for master base station, and one MAC entity forsecondary base station. In tight interworking, the configured set ofserving cells for a UE may comprise of two subsets: the Master CellGroup (MCG) containing the serving cells of the master base station, andthe Secondary Cell Group (SCG) containing the serving cells of thesecondary base station. For a SCG, one or more of the following may beapplied: at least one cell in the SCG has a configured UL CC and one ofthem, named PSCell (or PCell of SCG, or sometimes called PCell), isconfigured with PUCCH resources; when the SCG is configured, there maybe at least one SCG bearer or one split bearer; upon detection of aphysical layer problem or a random access problem on a PSCell, or themaximum number of (NR) RLC retransmissions has been reached associatedwith the SCG, or upon detection of an access problem on a PSCell duringa SCG addition or a SCG change: a RRC connection re-establishmentprocedure may not be triggered, UL transmissions towards cells of theSCG are stopped, a master base station may be informed by the UE of aSCG failure type, for split bearer, the DL data transfer over the masterbase station is maintained; the RLC AM bearer may be configured for thesplit bearer; like PCell, PSCell may not be de-activated; PSCell may bechanged with a SCG change (e.g. with security key change and a RACHprocedure); and/or neither a direct bearer type change between a Splitbearer and a SCG bearer nor simultaneous configuration of a SCG and aSplit bearer are supported.

With respect to the interaction between a master base station and asecondary base station, one or more of the following principles may beapplied: the master base station may maintain the RRM measurementconfiguration of the UE and may, (e.g., based on received measurementreports, traffic conditions, or bearer types), decide to ask a secondarybase station to provide additional resources (serving cells) for a UE;upon receiving a request from the master base station, a secondary basestation may create a container that may result in the configuration ofadditional serving cells for the UE (or decide that it has no resourceavailable to do so); for UE capability coordination, the master basestation may provide (part of) the AS configuration and the UEcapabilities to the secondary base station; the master base station andthe secondary base station may exchange information about a UEconfiguration by employing of RRC containers (inter-node messages)carried in Xn or Xx messages; the secondary base station may initiate areconfiguration of its existing serving cells (e.g., PUCCH towards thesecondary base station); the secondary base station may decide whichcell is the PSCell within the SCG; the master base station may notchange the content of the RRC configuration provided by the secondarybase station; in the case of a SCG addition and a SCG SCell addition,the master base station may provide the latest measurement results forthe SCG cell(s); both a master base station and a secondary base stationmay know the SFN and subframe offset of each other by OAM, (e.g., forthe purpose of DRX alignment and identification of a measurement gap).In an example, when adding a new SCG SCell, dedicated RRC signaling maybe used for sending required system information of the cell as for CA,except for the SFN acquired from a MIB of the PSCell of a SCG.

FIG. 13A and FIG. 13B are example diagrams for gNB deployment scenariosas per an aspect of an embodiment of the present disclosure. In thenon-centralized deployment scenario in FIG. 13A, the full protocol stack(e.g. NR RRC, NR PDCP, NR RLC, NR MAC, and NR PHY) may be supported atone node. In the centralized deployment scenario in FIG. 13B, upperlayers of gNB may be located in a Central Unit (CU), and lower layers ofgNB may be located in Distributed Units (DU). The CU-DU interface (e.g.Fs interface) connecting CU and DU may be ideal or non-ideal. Fs-C mayprovide a control plane connection over Fs interface, and Fs-U mayprovide a user plane connection over Fs interface. In the centralizeddeployment, different functional split options between CU and DUs may bepossible by locating different protocol layers (RAN functions) in CU andDU. The functional split may support flexibility to move RAN functionsbetween CU and DU depending on service requirements and/or networkenvironments. The functional split option may change during operationafter Fs interface setup procedure or may change only in Fs setupprocedure (i.e. static during operation after Fs setup procedure).

FIG. 14 is an example diagram for different functional split optionexamples of the centralized gNB deployment scenario as per an aspect ofan embodiment of the present disclosure. In the split option example 1,an NR RRC may be in CU, and NR PDCP, NR RLC, NR MAC, NR PHY, and RF maybe in DU. In the split option example 2, an NR RRC and NR PDCP may be inCU, and NR RLC, NR MAC, NR PHY, and RF may be in DU. In the split optionexample 3, an NR RRC, NR PDCP, and partial function of NR RLC may be inCU, and the other partial function of NR RLC, NR MAC, NR PHY, and RF maybe in DU. In the split option example 4, an NR RRC, NR PDCP, and NR RLCmay be in CU, and NR MAC, NR PHY, and RF may be in DU. In the splitoption example 5, an NR RRC, NR PDCP, NR RLC, and partial function of NRMAC may be in CU, and the other partial function of NR MAC, NR PHY, andRF may be in DU. In the split option example 6, an NR RRC, NR PDCP, NRRLC, and NR MAC may be in CU, and NR PHY and RF may be in DU. In thesplit option example 7, an NR RRC, NR PDCP, NR RLC, NR MAC, and partialfunction of NR PHY may be in CU, and the other partial function of NRPHY and RF may be in DU. In the split option example 8, an NR RRC, NRPDCP, NR RLC, NR MAC, and NR PHY may be in CU, and RF may be in DU.

The functional split may be configured per CU, per DU, per UE, perbearer, per slice, or with other granularities. In per CU split, a CUmay have a fixed split, and DUs may be configured to match the splitoption of CU. In per DU split, a DU may be configured with a differentsplit, and a CU may provide different split options for different DUs.In per UE split, a gNB (CU and DU) may provide different split optionsfor different UEs. In per bearer split, different split options may beutilized for different bearer types. In per slice splice, differentsplit options may be applied for different slices.

In an example embodiment, the new radio access network (new RAN) maysupport different network slices, which may allow differentiatedtreatment customized to support different service requirements with endto end scope. The new RAN may provide a differentiated handling oftraffic for different network slices that may be pre-configured and mayallow a single RAN node to support multiple slices. The new RAN maysupport selection of a RAN part for a given network slice, by one ormore slice ID(s) or NSSAI(s) provided by a UE or an NGC (e.g. NG CP).The slice ID(s) or NSSAI(s) may identify one or more of pre-configurednetwork slices in a PLMN. For initial attach, a UE may provide a sliceID and/or an NSSAI, and a RAN node (e.g. gNB) may use the slice ID orthe NSSAI for routing an initial NAS signaling to an NGC control planefunction (e.g. NG CP). If a UE does not provide any slice ID or NSSAI, aRAN node may send a NAS signaling to a default NGC control planefunction. For subsequent accesses, the UE may provide a temporary ID fora slice identification, which may be assigned by the NGC control planefunction, to enable a RAN node to route the NAS message to a relevantNGC control plane function. The new RAN may support resource isolationbetween slices. The RAN resource isolation may be achieved by avoidingthat shortage of shared resources in one slice breaks a service levelagreement for another slice.

The amount of data traffic carried over cellular networks is expected toincrease for many years to come. The number of users/devices isincreasing, and each user/device accesses an increasing number andvariety of services, e.g. video delivery, large files, images. Thisrequires not only high capacity in the network, but also provisioningvery high data rates to meet customers' expectations on interactivityand responsiveness. More spectrum is therefore needed for cellularoperators to meet the increasing demand. Considering user expectationsof high data rates along with seamless mobility, it is beneficial thatmore spectrum be made available for deploying macro cells as well assmall cells for cellular systems.

Striving to meet the market demands, there has been increasing interestfrom operators in deploying some complementary access utilizingunlicensed spectrum to meet the traffic growth. This is exemplified bythe large number of operator-deployed Wi-Fi networks and the 3GPPstandardization of LTE/WLAN interworking solutions. This interestindicates that unlicensed spectrum, when present, may be an effectivecomplement to licensed spectrum for cellular operators to helpaddressing the traffic explosion in some scenarios, such as hotspotareas. LAA offers an alternative for operators to make use of unlicensedspectrum while managing one radio network, thus offering newpossibilities for optimizing the network's efficiency.

In an example embodiment, Listen-before-talk (clear channel assessment)may be implemented for transmission in an LAA cell. In alisten-before-talk (LBT) procedure, equipment may apply a clear channelassessment (CCA) check before using the channel. For example, the CCAutilizes at least energy detection to determine the presence or absenceof other signals on a channel in order to determine if a channel isoccupied or clear, respectively. For example, European and Japaneseregulations mandate the usage of LBT in the unlicensed bands. Apart fromregulatory requirements, carrier sensing via LBT may be one way for fairsharing of the unlicensed spectrum.

In an example embodiment, discontinuous transmission on an unlicensedcarrier with limited maximum transmission duration may be enabled. Someof these functions may be supported by one or more signals to betransmitted from the beginning of a discontinuous LAA downlinktransmission. Channel reservation may be enabled by the transmission ofsignals, by an LAA node, after gaining channel access via a successfulLBT operation, so that other nodes that receive the transmitted signalwith energy above a certain threshold sense the channel to be occupied.Functions that may need to be supported by one or more signals for LAAoperation with discontinuous downlink transmission may include one ormore of the following: detection of the LAA downlink transmission(including cell identification) by wireless devices; time & frequencysynchronization of wireless devices.

In an example embodiment, DL LAA design may employ subframe boundaryalignment according to LTE-A carrier aggregation timing relationshipsacross serving cells aggregated by CA. This may not imply that the basestation transmissions may start only at the subframe boundary. LAA maysupport transmitting PDSCH when not all OFDM symbols are available fortransmission in a subframe according to LBT. Delivery of necessarycontrol information for the PDSCH may also be supported.

LBT procedure may be employed for fair and friendly coexistence of LAAwith other operators and technologies operating in unlicensed spectrum.LBT procedures on a node attempting to transmit on a carrier inunlicensed spectrum require the node to perform a clear channelassessment to determine if the channel is free for use. An LBT proceduremay involve at least energy detection to determine if the channel isbeing used. For example, regulatory requirements in some regions, e.g.,in Europe, specify an energy detection threshold such that if a nodereceives energy greater than this threshold, the node assumes that thechannel is not free. While nodes may follow such regulatoryrequirements, a node may optionally use a lower threshold for energydetection than that specified by regulatory requirements. In an example,LAA may employ a mechanism to adaptively change the energy detectionthreshold, e.g., LAA may employ a mechanism to adaptively lower theenergy detection threshold from an upper bound. Adaptation mechanism maynot preclude static or semi-static setting of the threshold. In anexample Category 4 LBT mechanism or other type of LBT mechanisms may beimplemented.

Various example LBT mechanisms may be implemented. In an example, forsome signals, in some implementation scenarios, in some situations,and/or in some frequencies no LBT procedure may performed by thetransmitting entity. In an example, Category 2 (e.g. LBT without randomback-off) may be implemented. The duration of time that the channel issensed to be idle before the transmitting entity transmits may bedeterministic. In an example, Category 3 (e.g. LBT with random back-offwith a contention window of fixed size) may be implemented. The LBTprocedure may have the following procedure as one of its components. Thetransmitting entity may draw a random number N within a contentionwindow. The size of the contention window may be specified by theminimum and maximum value of N. The size of the contention window may befixed. The random number N may be employed in the LBT procedure todetermine the duration of time that the channel is sensed to be idlebefore the transmitting entity transmits on the channel. In an example,Category 4 (e.g. LBT with random back-off with a contention window ofvariable size) may be implemented. The transmitting entity may draw arandom number N within a contention window. The size of contentionwindow may be specified by the minimum and maximum value of N. Thetransmitting entity may vary the size of the contention window whendrawing the random number N. The random number N is used in the LBTprocedure to determine the duration of time that the channel is sensedto be idle before the transmitting entity transmits on the channel

LAA may employ uplink LBT at the wireless device. The UL LBT scheme maybe different from the DL LBT scheme (e.g. by using different LBTmechanisms or parameters) for example, since the LAA UL is based onscheduled access which affects a wireless device's channel contentionopportunities. Other considerations motivating a different UL LBT schemeinclude, but are not limited to, multiplexing of multiple wirelessdevices in a single subframe.

In an example, a DL transmission burst may be a continuous transmissionfrom a DL transmitting node with no transmission immediately before orafter from the same node on the same CC. An UL transmission burst from awireless device perspective may be a continuous transmission from awireless device with no transmission immediately before or after fromthe same wireless device on the same CC. In an example, UL transmissionburst is defined from a wireless device perspective. In an example, anUL transmission burst may be defined from a base station perspective. Inan example, in case of a base station operating DL+UL LAA over the sameunlicensed carrier, DL transmission burst(s) and UL transmissionburst(s) on LAA may be scheduled in a TDM manner over the sameunlicensed carrier. For example, an instant in time may be part of a DLtransmission burst or an UL transmission burst.

A New Radio (NR) system may support both single beam and multi-beamoperations. In a multi-beam system, a base station (e.g., gNB) mayperform a downlink beam sweeping to provide coverage for downlinkSynchronization Signals (SS s) and common control channels. A UserEquipment (UE) may perform an uplink beam sweeping for uplink directionto access a cell. In a single beam scenario, a gNB may configuretime-repetition transmission for one SS block, which may comprise atleast Primary Synchronization Signal (PSS), Secondary SynchronizationSignal (SSS), and Physical Broadcast Channel (PBCH), with a wide beam.In a multi-beam scenario, a gNB may configure at least some of thesesignals and physical channels in multiple beams. A UE may identify atleast OFDM symbol index, slot index in a radio frame and radio framenumber from an SS block.

In an example, in an RRC INACTIVE state or RRC IDLE state, a UE mayassume that SS blocks form an SS burst, and an SS burst set. An SS burstset may have a given periodicity. In multi-beam scenarios, SS blocks maybe transmitted in multiple beams, together forming an SS burst. One ormore SS blocks may be transmitted on one beam. A beam has a steeringdirection. If multiple SS bursts are transmitted with beams, these SSbursts together may form an SS burst set as shown in FIG. 15. A basestation 1501 (e.g., a gNB in NR) may transmit SS bursts 1502A to 1502Hduring time periods 1503. A plurality of these SS bursts may comprise anSS burst set, such as an SS burst set 1504 (e.g., SS bursts 1502A and1502E). An SS burst set may comprise any number of a plurality of SSbursts 1502A to 1502H. Each SS burst within an SS burst set maytransmitted at a fixed or variable periodicity during time periods 1503.

An SS may be based on Cyclic Prefix-Orthogonal Frequency DivisionMultiplexing (CP-OFDM). The SS may comprise at least two types ofsynchronization signals; NR-PSS (Primary synchronization signal) andNR-SSS (Secondary synchronization signal). NR-PSS may be defined atleast for initial symbol boundary synchronization to the NR cell. NR-SSSmay be defined for detection of NR cell ID or at least part of NR cellID. NR-SSS detection may be based on the fixed time/frequencyrelationship with NR-PSS resource position irrespective of duplex modeand beam operation type at least within a given frequency range and CPoverhead. Normal CP may be supported for NR-PSS and NR-SSS.

The NR may comprise at least one physical broadcast channel (NR-PBCH).When a gNB transmit (or broadcast) the NR-PBCH, a UE may decode theNR-PBCH based on the fixed relationship with NR-PSS and/or NR-SSSresource position irrespective of duplex mode and beam operation type atleast within a given frequency range and CP overhead. NR-PBCH may be anon-scheduled broadcast channel carrying at least a part of minimumsystem information with fixed payload size and periodicity predefined inthe specification depending on carrier frequency range.

In single beam and multi-beam scenarios, NR may comprise an SS blockthat may support time (frequency, and/or spatial) division multiplexingof NR-PSS, NR-SSS, and NR-PBCH. A gNB may transmit NR-PSS, NR-SSS and/orNR-PBCH within an SS block. For a given frequency band, an SS block maycorrespond to N OFDM symbols based on the default subcarrier spacing,and N may be a constant. The signal multiplexing structure may be fixedin NR. A wireless device may identify, e.g., from an SS block, an OFDMsymbol index, a slot index in a radio frame, and a radio frame numberfrom an SS block.

A NR may support an SS burst comprising one or more SS blocks. An SSburst set may comprise one or more SS bursts. For example, a number ofSS bursts within a SS burst set may be finite. From physical layerspecification perspective, NR may support at least one periodicity of SSburst set. From UE perspective, SS burst set transmission may beperiodic, and UE may assume that a given SS block is repeated with an SSburst set periodicity.

Within an SS burst set periodicity, NR-PBCH repeated in one or more SSblocks may change. A set of possible SS block time locations may bespecified per frequency band in an RRC message. The maximum number ofSS-blocks within SS burst set may be carrier frequency dependent. Theposition(s) of actual transmitted SS-blocks may be informed at least forhelping CONNECTED/IDLE mode measurement, for helping CONNECTED mode UEto receive downlink (DL) data/control in one or more SS-blocks, or forhelping IDLE mode UE to receive DL data/control in one or moreSS-blocks. A UE may not assume that the gNB transmits the same number ofphysical beam(s). A UE may not assume the same physical beam(s) acrossdifferent SS-blocks within an SS burst set. For an initial cellselection, UE may assume default SS burst set periodicity which may bebroadcast via an RRC message and frequency band-dependent. At least formulti-beams operation case, the time index of SS-block may be indicatedto the UE.

For CONNECTED and IDLE mode UEs, NR may support network indication of SSburst set periodicity and information to derive measurementtiming/duration (e.g., time window for NR-SS detection). A gNB mayprovide (e.g., via broadcasting an RRC message) one SS burst setperiodicity information per frequency carrier to UE and information toderive measurement timing/duration if possible. In case that one SSburst set periodicity and one information regarding timing/duration areindicated, a UE may assume the periodicity and timing/duration for allcells on the same carrier. If a gNB does not provide indication of SSburst set periodicity and information to derive measurementtiming/duration, a UE may assume a predefined periodicity, e.g., 5 ms,as the SS burst set periodicity. NR may support set of SS burst setperiodicity values for adaptation and network indication.

For initial access, a UE may assume a signal corresponding to a specificsubcarrier spacing of NR-PSS/SSS in a given frequency band given by a NRspecification. For NR-PSS, a Zadoff-Chu (ZC) sequence may be employed asa sequence for NR-PSS. NR may define at least one basic sequence lengthfor a SS in case of sequence-based SS design. The number of antenna portof NR-PSS may be 1. For NR-PBCH transmission, NR may support a fixednumber of antenna port(s). A UE may not be required for a blinddetection of NR-PBCH transmission scheme or number of antenna ports. AUE may assume the same PBCH numerology as that of NR-SS. For the minimumsystem information delivery, NR-PBCH may comprise a part of minimumsystem information. NR-PBCH contents may comprise at least a part of theSFN (system frame number) or CRC. A gNB may transmit the remainingminimum system information in shared downlink channel via NR-PDSCH.

In a multi-beam example, one or more of PSS, SSS, or PBCH signals may berepeated for a cell, e.g., to support cell selection, cell reselection,and/or initial access procedures. For an SS burst, an associated PBCH ora physical downlink shared channel (PDSCH) scheduling system informationmay be broadcasted by a base station to multiple wireless devices. ThePDSCH may be indicated by a physical downlink control channel (PDCCH) ina common search space. The system information may comprise a physicalrandom access channel (PRACH) configuration for a beam. For a beam, abase station (e.g., a gNB in NR) may have a RACH configuration which mayinclude a PRACH preamble pool, time and/or frequency radio resources,and other power related parameters. A wireless device may use a PRACHpreamble from a RACH configuration to initiate a contention-based RACHprocedure or a contention-free RACH procedure. A wireless device mayperform a 4-step RACH procedure, which may be a contention-based RACHprocedure or a contention-free RACH procedure. The wireless device mayselect a beam associated with an SS block that may have the bestreceiving signal quality. The wireless device may successfully detect acell identifier associated with the cell and decode system informationwith a RACH configuration. The wireless device may use one PRACHpreamble and select one PRACH resource from RACH resources indicated bythe system information associated with the selected beam. A PRACHresource may comprise at least one of: a PRACH index indicating a PRACHpreamble, a PRACH format, a PRACH numerology, time and/or frequencyradio resource allocation, power setting of a PRACH transmission, and/orother radio resource parameters. For a contention-free RACH procedure,the PRACH preamble and resource may be indicated in a DCI or other highlayer signaling.

In an example, a UE may detect one or more PSS/SSS/PBCH for cellselection/reselection and/or initial access procedures. PBCH, or aPhysical Downlink Shared Channel (PDSCH), indicated by a PhysicalDownlink Control Channel (PDCCH) in common search space, scheduling asystem information, such as System Information Block type 2 (SIB2), maybe broadcasted to multiple UEs. In an example, SIB2 may carry one ormore Physical Random Access Channel (PRACH) configuration. In anexample, a gNB may have one or more Random Access Channel (RACH)configuration which may include PRACH preamble pool, time/frequencyradio resources, and other power related parameters. A UE may select aPRACH preamble from a RACH configuration to initiate a contention-basedRACH procedure, or a contention-free RACH procedure.

In an example, a UE may perform a 4-step RACH procedure, which may be acontention-based or contention-free RACH procedure. A four-step randomaccess (RA) procedure may comprise RA preamble (RAP) transmission in thefirst step, random access response (RAR) transmission in the secondstep, scheduled transmission of one or more transport blocks (TBs) inthe third step, and contention resolution in the fourth step as shown inFIG. 16. Specifically, FIG. 16A shows a contention-based 4-step RAprocedure, and FIG. 16B shows a contention-free RA procedure.

In the first step, a UE may transmit a RAP using a configured RApreamble format with a Tx beam. RA channel (RACH) resource may bedefined as a time-frequency resource to transmit a RAP. Broadcast systeminformation may inform whether a UE needs to transmit one ormultiple/repeated preamble within a subset of RACH resources.

A base station may configure an association between DL signal/channel,and a subset of RACH resources and/or a subset of RAP indices, fordetermining the downlink (DL) transmission in the second step. Based onthe DL measurement and the corresponding association, a UE may selectthe subset of RACH resources and/or the subset of RAP indices. In anexample, there may be two RAP groups informed by broadcast systeminformation and one may be optional. If a base station configures thetwo groups in the four-step RA procedure, a UE may determine which groupthe UE selects a RAP from, based on the pathloss and a size of themessage to be transmitted by the UE in the third step. A base stationmay use a group type to which a RAP belongs as an indication of themessage size in the third step and the radio conditions at a UE. A basestation may broadcast the RAP grouping information along with one ormore thresholds on system information.

In the second step of the four-step RA procedure, a base station maytransmit a RA response (RAR) to the UE in response to reception of a RAPthat the UE transmits. A UE may monitor the PDCCH carrying a DCI, todetect RAR transmitted on a PDSCH in a RA Response window. The DCI maybe CRC-scrambled by the RA-RNTI (Random Access-Radio Network TemporaryIdentifier). RA-RNTI may be used on the PDCCH when Random AccessResponse messages are transmitted. It may unambiguously identify whichtime-frequency resource is used by the MAC entity to transmit the RandomAccess preamble. The RA Response window may start at the subframe thatcontains the end of a RAP transmission plus three subframes. The RAResponse window may have a length indicated by ra-ResponseWindowSize. AUE may compute the RA-RNTI associated with the PRACH in which the UEtransmits a RAP as: RA-RNTI=1+t_id+10*f_id, where t_id is an index of afirst subframe of a specified PRACH (0≤t_id<10), and f_id is an index ofa specified PRACH within the subframe, in ascending order of frequencydomain (0≤f_id<6). In an example, different types of UEs, e.g. NB-IoT,BL-UE, or UE-EC may employ different formulas for RA-RNTI calculations.

A UE may stop monitoring for RAR(s) after decoding of a MAC packet dataunit (PDU) for RAR comprising a RAP identifier (RAPID) that matches theRAP transmitted by the UE. The MAC PDU may comprise one or more MAC RARsand a MAC header that may comprise a subheader having a backoffindicator (BI) and one or more subheader that comprises RAPIDs.

FIG. 17 illustrates an example of a MAC PDU comprising a MAC header andMAC RARs for a four-step RA procedure. If a RAR comprises a RAPIDcorresponding to a RAP that a UE transmits, the UE may process the data,such as a timing advance (TA) command, a UL grant, and a TemporaryC-RNTI (TC-RNTI), in the RAR.

FIG. 18A, FIG. 18B and FIG. 18C show contents of a MAC RAR.Specifically, FIG. 18A shows the contents of a MAC RAR of a normal UE,FIG. 18B shows the contents of a MAC RAR of an MTC UE, and FIG. 18Cshows the contents of MAC RAR of a NB-IOT UE.

In the third step of the four-step RA procedure, a UE may adjust UL timealignment by using the TA value corresponding to the TA command in thereceived RAR in the second step and may transmit the one or more TBs toa base station using the UL resources assigned in the UL grant in thereceived RAR. The TBs that a UE transmits in the third step may compriseRRC signaling, such as RRC connection request, RRC connectionRe-establishment request, or RRC connection resume request, and a UEidentity. The identity transmitted in the third step is used as part ofthe contention-resolution mechanism in the fourth step.

The fourth step in the four-step RA procedure may comprise a DL messagefor contention resolution. In an example, one or more UEs may performsimultaneous RA attempts selecting the same RAP in the first step andreceive the same RAR with the same TC-RNTI in the second step. Thecontention resolution in the fourth step may be to ensure that a UE doesnot incorrectly use another UE Identity. The contention resolutionmechanism may be based on either C-RNTI on PDCCH or UE ContentionResolution Identity on DL-SCH, depending on whether a UE has a C-RNTI ornot. If a UE has C-RNTI, upon detection of C-RNTI on the PDCCH, the UEmay determine the success of RA procedure. If a UE does not have C-RNTIpre-assigned, the UE may monitor DL-SCH associated with TC-RNTI that abase station transmits in a RAR of the second step and compare theidentity in the data transmitted by the base station on DL-SCH in thefourth step with the identity that the UE transmits in the third step.If the two identities are identical, the UE may determine the success ofRA procedure and promote the TC-RNTI to the C-RNTI.

The forth step in the four-step RA procedure may allow HARQretransmission. A UE may start mac-ContentionResolutionTimer when the UEtransmits one or more TBs to a base station in the third step and mayrestart mac-ContentionResolutionTimer at each HARQ retransmission. Whena UE receives data on the DL resources identified by C-RNTI or TC-RNTIin the fourth step, the UE may stop the mac-ContentionResolutionTimer.If the UE does not detect the contention resolution identity thatmatches to the identity transmitted by the UE in the third step, the UEmay determine the failure of RA procedure and discard the TC-RNTI. Ifmac-ContentionResolutionTimer expires, the UE may determine the failureof RA procedure and discard the TC-RNTI. If the contention resolution isfailed, a UE may flush the HARQ buffer used for transmission of the MACPDU and may restart the four-step RA procedure from the first step. TheUE may delay the subsequent RAP transmission by the backoff timerandomly selected according to a uniform distribution between 0 and thebackoff parameter value corresponding the BI in the MAC PDU for RAR.

In a four-step RA procedure, the usage of the first two steps may be toobtain UL time alignment for a UE and obtain an uplink grant. The thirdand fourth steps may be used to setup RRC connections, and/or resolvecontention from different UEs.

FIG. 19 shows an example of a random access procedure (e.g., via a RACH)that may include sending, by a base station, one or more SS blocks. Awireless device 1920 (e.g., a UE) may transmit one or more preambles toa base station 1921 (e.g., a gNB in NR). Each preamble transmission bythe wireless device may be associated with a separate random accessprocedure, such as shown in FIG. 19. The random access procedure maybegin at step 1901 with a base station 1921 (e.g., a gNB in NR) sendinga first SS block to a wireless device 1921 (e.g., a UE). Any of the SSblocks may comprise one or more of a PSS, SSS, tertiary synchronizationsignal (TSS), or PBCH signal. The first SS block in step 1901 may beassociated with a first PRACH configuration. At step 1902, the basestation 1921 may send to the wireless device 1920 a second SS block thatmay be associated with a second PRACH configuration. At step 1903, thebase station 1921 may send to the wireless device 1920 a third SS blockthat may be associated with a third PRACH configuration. At step 1904,the base station 1921 may send to the wireless device 1920 a fourth SSblock that may be associated with a fourth PRACH configuration. Anynumber of SS blocks may be sent in the same manner in addition to, orreplacing, steps 1903 and 1904. An SS burst may comprise any number ofSS blocks. For example, SS burst 1910 comprises the three SS blocks sentduring steps 1902-1904.

The wireless device 1920 may send to the base station 1921 a preamble,at step 1905, e.g., after or in response to receiving one or more SSblocks or SS bursts. The preamble may comprise a PRACH preamble and maybe referred to as RA Msg 1. The PRACH preamble may be transmitted instep 1905 according to or based on a PRACH configuration that may bereceived in an SS block (e.g., one of the SS blocks from steps1901-1904) that may be determined to be the best SS block beam. Thewireless device 1920 may determine a best SS block beam from among SSblocks it may receive prior to sending the PRACH preamble. The basestation 1921 may send a random access response (RAR), which may bereferred to as RA Msg2, at step 1906, e.g., after or in response toreceiving the PRACH preamble. The RAR may be transmitted in step 1906via a DL beam that corresponds to the SS block beam associated with thePRACH configuration. The base station 1921 may determine the best SSblock beam from among SS blocks it previously sent prior to receivingthe PRACH preamble. The base station 1621 may receive the PRACH preambleaccording to or based on the PRACH configuration associated with thebest SS block beam.

The wireless device 1920 may send to the base station 1921 anRRCConnectionRequest and/or RRCConnectionResumeRequest message, whichmay be referred to as RA Msg3, at step 1907, e.g., after or in responseto receiving the RAR. The base station 1921 may send to the wirelessdevice 1920 an RRCConnectionSetup and/or RRCConnectionResume message,which may be referred to as RA Msg4, at step 1908, e.g., after or inresponse to receiving the RRCConnectionRequest and/orRRCConnectionResumeRequest message. The wireless device 1920 may send tothe base station 1921 an RRCConnectionSetupComplete and/orRRCConnectionResumeComplete message, which may be referred to as RAMsg5, at step 1909, e.g., after or in response to receiving theRRCConnectionSetup and/or RRCConnectionResume. An RRC connection may beestablished between the wireless device 1920 and the base station 1921,and the random access procedure may end, e.g., after or in response toreceiving the RRCConnectionSetupComplete and/orRRCConnectionResumeComplete message.

A best beam, including but not limited to a best SS block beam, may bedetermined based on a channel state information reference signal(CSI-RS). A wireless device may use a CSI-RS in a multi-beam system forestimating the beam quality of the links between the wireless device anda base station. For example, based on a measurement of a CSI-RS, awireless device may report CSI for downlink channel adaption. A CSIparameter may include a precoding matrix index (PMI), a channel qualityindex (CQI) value, and/or a rank indicator (RI). A wireless device mayreport a beam index based on a reference signal received power (RSRP)measurement on a CSI-RS. The wireless device may report the beam indexin a CSI resource indication (CRI) for downlink beam selection. A basestation may transmit a CSI-RS via a CSI-RS resource, such as via one ormore antenna ports, or via one or more time and/or frequency radioresources. A beam may be associated with a CSI-RS. A CSI-RS may comprisean indication of a beam direction. Each of a plurality of beams may beassociated with one of a plurality of CSI-RSs. A CSI-RS resource may beconfigured in a cell-specific way, e.g., via common RRC signaling.Additionally or alternatively, a CSI-RS resource may be configured in awireless device-specific way, e.g., via dedicated RRC signaling and/orlayer 1 and/or layer 2 (L1/L2) signaling. Multiple wireless devices inor served by a cell may measure a cell-specific CSI-RS resource. Adedicated subset of wireless devices in or served by a cell may measurea wireless device-specific CSI-RS resource. A base station may transmita CSI-RS resource periodically, using aperiodic transmission, or using amulti-shot or semi-persistent transmission. In a periodic transmission,a base station may transmit the configured CSI-RS resource using aconfigured periodicity in the time domain. In an aperiodic transmission,a base station may transmit the configured CSI-RS resource in adedicated time slot. In a multi-shot or semi-persistent transmission, abase station may transmit the configured CSI-RS resource in a configuredperiod. A base station may configure different CSI-RS resources indifferent terms for different purposes. Different terms may include,e.g., cell-specific, device-specific, periodic, aperiodic, multi-shot,or other terms. Different purposes may include, e.g., beam management,CQI reporting, or other purposes.

FIG. 20 shows an example of transmitting CSI-RSs periodically for abeam. A base station 2001 may transmit a beam in a predefined order inthe time domain, such as during time periods 2003. Beams used for aCSI-RS transmission, such as for CSI-RS 2004 in transmissions 2002Cand/or 2003E, may have a different beam width relative to a beam widthfor SS-blocks transmission, such as for SS blocks 2002A, 2002B, 2002D,and 2002F-2002H. Additionally or alternatively, a beam width of a beamused for a CSI-RS transmission may have the same value as a beam widthfor an SS block. Some or all of one or more CSI-RSs may be included inone or more beams. An SS block may occupy a number of OFDM symbols(e.g., 4), and a number of subcarriers (e.g., 240), carrying asynchronization sequence signal. The synchronization sequence signal mayidentify a cell.

FIG. 21 shows an example of a CSI-RS that may be mapped in time andfrequency domains. Each square shown in FIG. 21 may represent a resourceblock within a bandwidth of a cell. Each resource block may comprise anumber of subcarriers. A cell may have a bandwidth comprising a numberof resource blocks. A base station (e.g., a gNB in NR) may transmit oneor more Radio Resource Control (RRC) messages comprising CSI-RS resourceconfiguration parameters for one or more CSI-RS. One or more of thefollowing parameters may be configured by higher layer signaling foreach CSI-RS resource configuration: CSI-RS resource configurationidentity, number of CSI-RS ports, CSI-RS configuration (e.g., symbol andRE locations in a subframe), CSI-RS subframe configuration (e.g.,subframe location, offset, and periodicity in a radio frame), CSI-RSpower parameter, CSI-RS sequence parameter, CDM type parameter,frequency density, transmission comb, QCL parameters (e.g.,QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist,csi-rs-configZPid, qcl-csi-rs-configNZPid), and/or other radio resourceparameters.

FIG. 21 shows three beams that may be configured for a wireless device,e.g., in a wireless device-specific configuration. Any number ofadditional beams (e.g., represented by the column of blank squares) orfewer beams may be included. Beam 1 may be allocated with CSI-RS 1 thatmay be transmitted in some subcarriers in a resource block (RB) of afirst symbol. Beam 2 may be allocated with CSI-RS 2 that may betransmitted in some subcarriers in an RB of a second symbol. Beam 3 maybe allocated with CSI-RS 3 that may be transmitted in some subcarriersin an RB of a third symbol. All subcarriers in an RB may not necessarilybe used for transmitting a particular CSI-RS (e.g., CSI-RS 1) on anassociated beam (e.g., beam 1) for that CSI-RS. By using frequencydivision multiplexing (FDM), other subcarriers, not used for beam 1 forthe wireless device in the same RB, may be used for other CSI-RStransmissions associated with a different beam for other wirelessdevices. Additionally or alternatively, by using time domainmultiplexing (TDM), beams used for a wireless device may be configuredsuch that different beams (e.g., beam 1, beam 2, and beam 3) for thewireless device may be transmitted using some symbols different frombeams of other wireless devices.

Beam management may use a device-specific configured CSI-RS. In a beammanagement procedure, a wireless device may monitor a channel quality ofa beam pair link comprising a transmitting beam by a base station (e.g.,a gNB in NR) and a receiving beam by the wireless device (e.g., a UE).When multiple CSI-RSs associated with multiple beams are configured, awireless device may monitor multiple beam pair links between the basestation and the wireless device.

A wireless device may transmit one or more beam management reports to abase station. A beam management report may indicate one or more beampair quality parameters, comprising, e.g., one or more beamidentifications, RSRP, PMI, CQI, and/or RI, of a subset of configuredbeams.

A base station and/or a wireless device may perform a downlink L1/L2beam management procedure. One or more downlink L1/L2 beam managementprocedures may be performed within one or multiple transmission andreceiving points (TRPs), such as shown in FIG. 23A and FIG. 23B,respectively.

FIG. 22 shows examples of three beam management procedures, P1, P2, andP3. Procedure P1 may be used to enable a wireless device measurement ondifferent transmit (Tx) beams of a TRP (or multiple TRPs), e.g., tosupport a selection of Tx beams and/or wireless device receive (Rx)beam(s) (shown as ovals in the top row and bottom row, respectively, ofP1). Beamforming at a TRP (or multiple TRPs) may include, e.g., anintra-TRP and/or inter-TRP Tx beam sweep from a set of different beams(shown, in the top rows of P1 and P2, as ovals rotated in acounter-clockwise direction indicated by the dashed arrow). Beamformingat a wireless device 2201, may include, e.g., a wireless device Rx beamsweep from a set of different beams (shown, in the bottom rows of P1 andP3, as ovals rotated in a clockwise direction indicated by the dashedarrow). Procedure P2 may be used to enable a wireless device measurementon different Tx beams of a TRP (or multiple TRPs) (shown, in the top rowof P2, as ovals rotated in a counter-clockwise direction indicated bythe dashed arrow), e.g., which may change inter-TRP and/or intra-TRP Txbeam(s). Procedure P2 may be performed, e.g., on a smaller set of beamsfor beam refinement than in procedure P1. P2 may be a particular exampleof P1. Procedure P3 may be used to enable a wireless device measurementon the same Tx beam (shown as oval in P3), e.g., to change a wirelessdevice Rx beam if the wireless device 2201 uses beamforming

A wireless device 2201 (e.g., a UE) and/or a base station 2202 (e.g., agNB) may trigger a beam failure recovery mechanism. The wireless device2201 may trigger a beam failure recovery (BFR) request transmission,e.g., if a beam failure event occurs. A beam failure event may include,e.g., a determination that a quality of beam pair link(s) of anassociated control channel is unsatisfactory. A determination of anunsatisfactory quality of beam pair link(s) of an associated channel maybe based on the quality falling below a threshold and/or an expirationof a timer.

The wireless device 2201 may measure a quality of beam pair link(s)using one or more reference signals (RS). One or more SS blocks, one ormore CSI-RS resources, and/or one or more demodulation reference signals(DM-RSs) of a PBCH may be used as a RS for measuring a quality of a beampair link. Each of the one or more CSI-RS resources may be associatedwith a CSI-RS resource index (CRI). A quality of a beam pair link may bebased on one or more of an RSRP value, reference signal received quality(RSRQ) value, and/or CSI value measured on RS resources. The basestation 2202 may indicate that an RS resource, e.g., that may be usedfor measuring a beam pair link quality, is quasi-co-located (QCLed) withone or more DM-RSs of a control channel. The RS resource and the DM-RSsof the control channel may be QCLed when the channel characteristicsfrom a transmission via an RS to the wireless device 2201, and thechannel characteristics from a transmission via a control channel to thewireless device, are similar or the same under a configured criterion.

FIG. 23A shows an example of a beam failure event involving a singleTRP. A single TRP such as at a base station 2301 may transmit, to awireless device 2302, a first beam 2303 and a second beam 2304. A beamfailure event may occur if, e.g., a serving beam, such as the secondbeam 2304, is blocked by a moving vehicle 2305 or other obstruction(e.g., building, tree, land, or any object) and configured beams (e.g.,the first beam 2303 and/or the second beam 2304), including the servingbeam, are received from the single TRP. The wireless device 2302 maytrigger a mechanism to recover from beam failure when a beam failureoccurs.

FIG. 23B shows an example of a beam failure event involving multipleTRPs. Multiple TRPs, such as at a first base station 2306 and at asecond base station 2309, may transmit, to a wireless device 2308, afirst beam 2307 (e.g., from the first base station 2306) and a secondbeam 2310 (e.g., from the second base station 2309). A beam failureevent may occur when, e.g., a serving beam, such as the second beam2310, is blocked by a moving vehicle 2311 or other obstruction (e.g.,building, tree, land, or any object) and configured beams (e.g., thefirst beam 2307 and/or the second beam 2310) are received from multipleTRPs. The wireless device 2008 may trigger a mechanism to recover frombeam failure when a beam failure occurs.

A wireless device may monitor a PDCCH, such as a New Radio PDCCH(NR-PDCCH), on M beam pair links simultaneously, where M>1 and themaximum value of M may depend at least on the wireless devicecapability. Such monitoring may increase robustness against beam pairlink blocking. A base station may transmit, and the wireless device mayreceive, one or more messages configured to cause the wireless device tomonitor NR-PDCCH on different beam pair link(s) and/or in differentNR-PDCCH OFDM symbol.

A base station may transmit higher layer signaling, and/or a MAC controlelement (MAC CE), that may comprise parameters related to a wirelessdevice Rx beam setting for monitoring NR-PDCCH on multiple beam pairlinks. A base station may transmit one or more indications of a spatialQCL assumption between a first DL RS antenna port(s) and a second DL RSantenna port(s). The first DL RS antenna port(s) may be for one or moreof a cell-specific CSI-RS, device-specific CSI-RS, SS block, PBCH withDM-RSs of PBCH, and/or PBCH without DM-RSs of PBCH. The second DL RSantenna port(s) may be for demodulation of a DL control channelSignaling for a beam indication for a NR-PDCCH (e.g., configuration tomonitor NR-PDCCH) may be via MAC CE signaling, RRC signaling, DCIsignaling, or specification-transparent and/or an implicit method, andany combination thereof.

For reception of unicast DL data channel, a base station may indicatespatial QCL parameters between DL RS antenna port(s) and DM-RS antennaport(s) of DL data channel. A base station may transmit DCI (e.g.,downlink grants) comprising information indicating the RS antennaport(s). The information may indicate the RS antenna port(s) which maybe QCLed with DM-RS antenna port(s). A different set of DM-RS antennaport(s) for the DL data channel may be indicated as a QCL with adifferent set of RS antenna port(s).

If a base station transmits a signal indicating a spatial QCL parametersbetween CSI-RS and DM-RS for PDCCH, a wireless device may use CSI-RSsQCLed with DM-RS for a PDCCH to monitor beam pair link quality. If abeam failure event occurs, the wireless device may transmit a beamfailure recovery request, such as by a determined configuration.

If a wireless device transmits a beam failure recovery request, e.g.,via an uplink physical channel or signal, a base station may detect thatthere is a beam failure event, for the wireless device, by monitoringthe uplink physical channel or signal. The base station may initiate abeam recovery mechanism to recover the beam pair link for transmittingPDCCH between the base station and the wireless device. The base stationmay transmit one or more control signals, to the wireless device, e.g.,after or in response to receiving the beam failure recovery request. Abeam recovery mechanism may be, e.g., an L1 scheme, or a higher layerscheme.

A base station may transmit one or more messages comprising, e.g.,configuration parameters of an uplink physical channel and/or a signalfor transmitting a beam failure recovery request. The uplink physicalchannel and/or signal may be based on at least one of the following: anon-contention based PRACH (e.g., a beam failure recovery PRACH orBFR-PRACH), which may use a resource orthogonal to resources of otherPRACH transmissions; a PUCCH (e.g., beam failure recovery PUCCH orBFR-PUCCH); and/or a contention-based PRACH resource. Combinations ofthese candidate signal and/or channels may be configured by a basestation.

A gNB may respond a confirmation message to a UE after receiving one ormultiple BFR request. The confirmation message may include the CRIassociated with the candidate beam the UE indicates in the one ormultiple BFR request. The confirmation message may be a L1 controlinformation.

In carrier aggregation (CA), two or more component carriers (CCs) may beaggregated. A wireless device may simultaneously receive or transmit onone or more CCs, depending on capabilities of the wireless device, usingthe technique of CA. In an example, a wireless device may support CA forcontiguous CCs and/or for non-contiguous CCs. CCs may be organized intocells. For example, CCs may be organized into one primary cell (PCell)and one or more secondary cells (SCells).

When configured with CA, a wireless device may have one RRC connectionwith a network. During an RRC connectionestablishment/re-establishment/handover, a cell providing NAS mobilityinformation may be a serving cell. During an RRC connectionre-establishment/handover procedure, a cell providing a security inputmay be a serving cell. In an example, the serving cell may denote aPCell. In an example, a gNB may transmit, to a wireless device, one ormore messages comprising configuration parameters of a plurality of oneor more SCells, depending on capabilities of the wireless device.

When configured with CA, a base station and/or a wireless device mayemploy an activation/deactivation mechanism of an SCell to improvebattery or power consumption of the wireless device. When a wirelessdevice is configured with one or more SCells, a gNB may activate ordeactivate at least one of the one or more SCells. Upon configuration ofan SCell, the SCell may be deactivated unless an SCell state associatedwith the SCell is set to “activated” or “dormant”.

In an example, a wireless device may activate/deactivate an SCell inresponse to receiving an SCell Activation/Deactivation MAC CE.

In an example, a gNB may transmit, to a wireless device, one or moremessages comprising an SCell timer (e.g., sCellDeactivationTimer). In anexample, a wireless device may deactivate an SCell in response to anexpiry of the SCell timer.

When a wireless device receives an SCell Activation/Deactivation MAC CEactivating an SCell, the wireless device may activate the SCell. Inresponse to the activating the SCell, the wireless device may performoperations comprising: SRS transmissions on the SCell; CQI/PMI/RI/CRIreporting for the SCell; PDCCH monitoring on the SCell; PDCCH monitoringfor the SCell; and/or PUCCH transmissions on the SCell.

In an example, in response to the activating the SCell, the wirelessdevice may start or restart a first SCell timer (e.g.,sCellDeactivationTimer) associated with the SCell. The wireless devicemay start or restart the first SCell timer in the slot when the SCellActivation/Deactivation MAC CE activating the SCell has been received.In an example, in response to the activating the SCell, the wirelessdevice may (re-)initialize one or more suspended configured uplinkgrants of a configured grant Type 1 associated with the SCell accordingto a stored configuration. In an example, in response to the activatingthe SCell, the wireless device may trigger PHR.

When a wireless device receives an SCell Activation/Deactivation MAC CEdeactivating an activated SCell, the wireless device may deactivate theactivated SCell. In an example, when a first SCell timer (e.g.,sCellDeactivationTimer) associated with an activated SCell expires, thewireless device may deactivate the activated SCell. In response to thedeactivating the activated SCell, the wireless device may stop the firstSCell timer associated with the activated SCell. In an example, inresponse to the deactivating the activated S Cell, the wireless devicemay clear one or more configured downlink assignments, and/or one ormore configured uplink grants of a configured uplink grant Type 2associated with the activated SCell. In an example, in response to thedeactivating the activated SCell, the wireless device may: suspend oneor more configured uplink grants of a configured uplink grant Type 1associated with the activated SCell; and/or flush HARQ buffersassociated with the activated SCell.

In an example, when an SCell is deactivated, a wireless device may notperform operations comprising: transmitting SRS on the SCell; reportingCQI/PMI/RI/CRI for the SCell; transmitting on UL-SCH on the SCell;transmitting on RACH on the SCell; monitoring at least one first PDCCHon the SCell; monitoring at least one second PDCCH for the SCell; and/ortransmitting a PUCCH on the SCell.

In an example, when at least one first PDCCH on an activated SCellindicates an uplink grant or a downlink assignment, a wireless devicemay restart a first SCell timer (e.g., sCellDeactivationTimer)associated with the activated SCell. In an example, when at least onesecond PDCCH on a serving cell (e.g. a PCell or an SCell configured withPUCCH, i.e. PUCCH SCell) scheduling the activated SCell indicates anuplink grant or a downlink assignment for the activated SCell, awireless device may restart the first SCell timer (e.g.,sCellDeactivationTimer) associated with the activated SCell.

In an example, when an SCell is deactivated, if there is an ongoingrandom access procedure on the SCell, a wireless device may abort theongoing random access procedure on the SCell.

FIG. 24A shows an example of an SCell Activation/Deactivation MAC CE ofone octet. A first MAC PDU subheader with a first LCID (e.g., ‘111010’)may identify the SCell Activation/Deactivation MAC CE of one octet. TheSCell Activation/Deactivation MAC CE of one octet may have a fixed size.The SCell Activation/Deactivation MAC CE of one octet may comprise asingle octet. The single octet may comprise a first number of C-fields(e.g. seven) and a second number of R-fields (e.g., one).

FIG. 24B shows an example of an SCell Activation/Deactivation MAC CE offour octets. A second MAC PDU subheader with a second LCID (e.g.,‘111001’) may identify the SCell Activation/Deactivation MAC CE of fouroctets. The SCell Activation/Deactivation MAC CE of four octets may havea fixed size. The SCell Activation/Deactivation MAC CE of four octetsmay comprise four octets. The four octets may comprise a third number ofC-fields (e.g., 31) and a fourth number of R-fields (e.g., 1).

In FIG. 24A and/or FIG. 24B, a C_(i) field may indicate anactivation/deactivation status of an SCell with an SCell index i if anSCell with SCell index i is configured. In an example, when the C_(i)field is set to one, an SCell with an SCell index i may be activated. Inan example, when the C_(i) field is set to zero, an SCell with an SCellindex i may be deactivated. In an example, if there is no SCellconfigured with SCell index i, the wireless device may ignore the C_(i)field. In FIG. 24A and FIG. 24B, an R field may indicate a reserved bit.The R field may be set to zero.

FIG. 25A and FIG. 25B show timeline when a UE receives a MAC activationcommand. When a UE receives a MAC activation command for a secondarycell in subframe n, the corresponding actions in the MAC layer shall beapplied no later than the minimum requirement defined in 3GPP TS 36.133or TS 38.133 and no earlier than subframe n+8, except for the following:the actions related to CSI reporting and the actions related to thesCellDeactivationTimer associated with the secondary cell, which shallbe applied in subframe n+8. When a UE receives a MAC deactivationcommand for a secondary cell or the sCellDeactivationTimer associatedwith the secondary cell expires in subframe n, the corresponding actionsin the MAC layer shall apply no later than the minimum requirementdefined in 3GPP TS 36.133 or TS 38.133, except for the actions relatedto CSI reporting which shall be applied in subframe n+8.

When a UE receives a MAC activation command for a secondary cell insubframe n, the actions related to CSI reporting and the actions relatedto the sCellDeactivationTimer associated with the secondary cell, areapplied in subframe n+8. When a UE receives a MAC deactivation commandfor a secondary cell or other deactivation conditions are met (e.g. thesCellDeactivationTimer associated with the secondary cell expires) insubframe n, the actions related to CSI reporting are applied in subframen+8. The UE starts reporting invalid or valid CSI for the SCell at the(n+8)^(th) subframe, and start or restart the sCellDeactivationTimerwhen receiving the MAC CE activating the SCell in the n^(th) subframe.For some UE having slow activation, it may report an invalid CSI(out-of-range CSI) at the (n+8)^(th) subframe, for some UE having aquick activation, it may report a valid CSI at the (n+8)^(th) subframe.

When a UE receives a MAC activation command for an SCell in subframe n,the UE starts reporting CQI/PMI/RI/PTI for the SCell at subframe n+8 andstarts or restarts the sCellDeactivationTimer associated with the SCellat subframe n+8. It is important to define the timing of these actionsfor both UE and eNB. For example, sCellDeactivationTimer is maintainedin both eNB and UE and it is important that both UE and eNB stop, startand/or restart this timer in the same TTI. Otherwise, thesCellDeactivationTimer in the UE may not be in-sync with thecorresponding sCellDeactivationTimer in the eNB. Also, eNB startsmonitoring and receiving CSI (CQI/PMI/RI/PTI) according to thepredefined timing in the same TTI and/or after UE starts transmittingthe CSI. If the CSI timings in UE and eNB are not coordinated based on acommon standard or air interface signaling the network operation mayresult in inefficient operations and/or errors.

FIG. 26 shows DCI formats for an example of 20 MHz FDD operation with 2Tx antennas at the base station and no carrier aggregation in an LTEsystem. In a NR system, the DCI formats may comprise at least one of:DCI format 0_0/0_1 indicating scheduling of PUSCH in a cell; DCI format1_0/1_1 indicating scheduling of PDSCH in a cell; DCI format 2_0notifying a group of UEs of slot format; DCI format 2_1 notifying agroup of UEs of PRB(s) and OFDM symbol(s) where a UE may assume notransmission is intended for the UE; DCI format 2_2 indicatingtransmission of TPC commands for PUCCH and PUSCH; and/or DCI format 2_3indicating transmission of a group of TPC commands for SRS transmissionby one or more UEs. In an example, a gNB may transmit a DCI via a PDCCHfor scheduling decision and power-control commends. More specifically,the DCI may comprise at least one of: downlink scheduling assignments,uplink scheduling grants, power-control commands. The downlinkscheduling assignments may comprise at least one of: PDSCH resourceindication, transport format, HARQ information, and control informationrelated to multiple antenna schemes, a command for power control of thePUCCH used for transmission of ACK/NACK in response to downlinkscheduling assignments. The uplink scheduling grants may comprise atleast one of: PUSCH resource indication, transport format, and HARQrelated information, a power control command of the PUSCH.

In an example, different types of control information may correspond todifferent DCI message sizes. For example, supporting spatialmultiplexing with noncontiguous allocation of RBs in the frequencydomain may require a larger scheduling message in comparison with anuplink grant allowing for frequency-contiguous allocation only. DCIs maybe categorized into different DCI formats, where a format corresponds toa certain message size and usage.

In an example, a UE may monitor one or more PDCCH to detect one or moreDCI with one or more DCI format. The one or more PDCCH may betransmitted in common search space or UE-specific search space. A UE maymonitor PDCCH with only a limited set of DCI format, to save powerconsumption. For example, a normal UE may not be required to detect aDCI with DCI format 6 which is used for an eMTC UE. The more DCI formatto be detected, the more power be consumed at the UE.

In an example, a UE may monitor one or more PDCCH candidates to detectone or more DCI with one or more DCI format. The one or more PDCCH maybe transmitted in common search space or UE-specific search space. A UEmay monitor PDCCH with only a limited set of DCI format, to save powerconsumption. For example, a normal UE may not be required to detect aDCI with DCI format 6 which is used for an eMTC UE. The more DCI formatto be detected, the more power be consumed at the UE.

In an example, the one or more PDCCH candidates that a UE monitors maybe defined in terms of PDCCH UE-specific search spaces. A PDCCHUE-specific search space at CCE aggregation level L∈{1, 2, 4, 8} may bedefined by a set of PDCCH candidates for CCE aggregation level L. In anexample, for a DCI format, a UE may be configured per serving cell byone or more higher layer parameters a number of PDCCH candidates per CCEaggregation level L.

In an example, in non-DRX mode operation, a UE may monitor one or morePDCCH candidate in control resource set q according to a periodicity ofW_(PDCCH, q) symbols that may be configured by one or more higher layerparameters for control resource set q.

In an example, if a UE is configured with higher layer parameter, e.g.,cif-InSchedulingCell, the carrier indicator field value may correspondto cif-InSchedulingCell.

In an example, for the serving cell on which a UE may monitor one ormore PDCCH candidate in a UE-specific search space, if the UE is notconfigured with a carrier indicator field, the UE may monitor the one ormore PDCCH candidates without carrier indicator field. In an example,for the serving cell on which a UE may monitor one or more PDCCHcandidates in a UE-specific search space, if a UE is configured with acarrier indicator field, the UE may monitor the one or more PDCCHcandidates with carrier indicator field.

In an example, a UE may not monitor one or more PDCCH candidates on asecondary cell if the UE is configured to monitor one or more PDCCHcandidates with carrier indicator field corresponding to that secondarycell in another serving cell. For example, for the serving cell on whichthe UE may monitor one or more PDCCH candidates, the UE may monitor theone or more PDCCH candidates at least for the same serving cell.

In an example, the information in the DCI formats used for downlinkscheduling can be organized into different groups, with the fieldpresent varying between the DCI formats, including at least one of:resource information, consisting of: carrier indicator (0 or 3 bits), RBallocation; HARQ process number; MCS, NDI, and RV (for the first TB);MCS, NDI and RV (for the second TB); MIMO related information; PDSCHresource-element mapping and QCI; Downlink assignment index (DAI); TPCfor PUCCH; SRS request (1 bit), triggering one-shot SRS transmission;ACK/NACK offset; DCI format 0/1A indication, used to differentiatebetween DCI format 1A and 0; and padding if necessary. The MIMO relatedinformation may comprise at least one of: PMI, precoding information,transport block swap flag, power offset between PDSCH and referencesignal, reference-signal scrambling sequence, number of layers, and/orantenna ports for the transmission.

In an example, the information in the DCI formats used for uplinkscheduling can be organized into different groups, with the fieldpresent varying between the DCI formats, including at least one of:resource information, consisting of: carrier indicator, resourceallocation type, RB allocation; MCS, NDI (for the first TB); MCS, NDI(for the second TB); phase rotation of the uplink DMRS; precodinginformation; CSI request, requesting an aperiodic CSI report; SRSrequest (2 bit), used to trigger aperiodic SRS transmission using one ofup to three preconfigured settings; uplink index/DAI; TPC for PUSCH; DCIformat 0/1A indication; and padding if necessary.

In an example, a gNB may perform CRC scrambling for a DCI, beforetransmitting the DCI via a PDCCH. The gNB may perform CRC scrambling bybit-wise addition (or Modulo-2 addition or exclusive OR (XOR) operation)of multiple bits of at least one wireless device identifier (e.g.,C-RNTI, CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, SP CSIC-RNTI, SRS-TPC-RNTI, INT-RNTI, SFI-RNTI, P-RNTI, SI-RNTI, RA-RNTI,and/or MCS-C-RNTI) with the CRC bits of the DCI. The wireless device maycheck the CRC bits of the DCI, when detecting the DCI. The wirelessdevice may receive the DCI when the CRC is scrambled by a sequence ofbits that is the same as the at least one wireless device identifier.

In a NR system, in order to support wide bandwidth operation, a gNB maytransmit one or more PDCCH in different control resource sets. A gNB maytransmit one or more RRC message comprising configuration parameters ofone or more control resource sets. At least one of the one or morecontrol resource sets may comprise at least one of: a first OFDM symbol;a number of consecutive OFDM symbols; a set of resource blocks; aCCE-to-REG mapping; and a REG bundle size, in case of interleavedCCE-to-REG mapping.

In an example, a wireless device may transmit one or more uplink controlinformation (UCI) via one or more PUCCH resources to a base station. Theone or more UCI may comprise at least one of: HARQ-ACK information;scheduling request (SR); and/or CSI report. In an example, a PUCCHresource may be identified by at least: frequency location (e.g.,starting PRB); and/or a PUCCH format associated with initial cyclicshift of a base sequence and time domain location (e.g., starting symbolindex). In an example, a PUCCH format may be PUCCH format 0, PUCCHformat 1, PUCCH format 2, PUCCH format 3, or PUCCH format 4. A PUCCHformat 0 may have a length of 1 or 2 OFDM symbols and be less than orequal to 2 bits. A PUCCH format 1 may occupy a number between 4 and 14of OFDM symbols and be less than or equal to 2 bits. A PUCCH format 2may occupy 1 or 2 OFDM symbols and be greater than 2 bits. A PUCCHformat 3 may occupy a number between 4 and 14 of OFDM symbols and begreater than 2 bits. A PUCCH format 4 may occupy a number between 4 and14 of OFDM symbols and be greater than 2 bits. The PUCCH resource may beconfigured on a PCell, or a PUCCH secondary cell.

In an example, when configured with multiple uplink BWPs, a base stationmay transmit to a wireless device, one or more RRC messages comprisingconfiguration parameters of one or more PUCCH resource sets (e.g., atmost 4 sets) on an uplink BWP of the multiple uplink BWPs. Each PUCCHresource set may be configured with a PUCCH resource set index, a listof PUCCH resources with each PUCCH resource being identified by a PUCCHresource identifier (e.g., pucch-Resourceid), and/or a maximum number ofUCI information bits a wireless device may transmit using one of theplurality of PUCCH resources in the PUCCH resource set.

In an example, when configured with one or more PUCCH resource sets, awireless device may select one of the one or more PUCCH resource setsbased on a total bit length of UCI information bits (e.g., HARQ-ARQbits, SR, and/or CSI) the wireless device will transmit. In an example,when the total bit length of UCI information bits is less than or equalto 2, the wireless device may select a first PUCCH resource set with thePUCCH resource set index equal to “0”. In an example, when the total bitlength of UCI information bits is greater than 2 and less than or equalto a first configured value, the wireless device may select a secondPUCCH resource set with the PUCCH resource set index equal to “1”. In anexample, when the total bit length of UCI information bits is greaterthan the first configured value and less than or equal to a secondconfigured value, the wireless device may select a third PUCCH resourceset with the PUCCH resource set index equal to “2”. In an example, whenthe total bit length of UCI information bits is greater than the secondconfigured value and less than or equal to a third value (e.g., 1706),the wireless device may select a fourth PUCCH resource set with thePUCCH resource set index equal to “3”.

In an example, a wireless device may determine, based on a number ofuplink symbols of UCI transmission and a number of UCI bits, a PUCCHformat from a plurality of PUCCH formats comprising PUCCH format 0,PUCCH format 1, PUCCH format 2, PUCCH format 3 and/or PUCCH format 4. Inan example, the wireless device may transmit UCI in a PUCCH using PUCCHformat 0 if the transmission is over 1 symbol or 2 symbols and thenumber of HARQ-ACK information bits with positive or negative SR(HARQ-ACK/SR bits) is 1 or 2. In an example, the wireless device maytransmit UCI in a PUCCH using PUCCH format 1 if the transmission is over4 or more symbols and the number of HARQ-ACK/SR bits is 1 or 2. In anexample, the wireless device may transmit UCI in a PUCCH using PUCCHformat 2 if the transmission is over 1 symbol or 2 symbols and thenumber of UCI bits is more than 2. In an example, the wireless devicemay transmit UCI in a PUCCH using PUCCH format 3 if the transmission isover 4 or more symbols, the number of UCI bits is more than 2 and PUCCHresource does not include an orthogonal cover code. In an example, thewireless device may transmit UCI in a PUCCH using PUCCH format 4 if thetransmission is over 4 or more symbols, the number of UCI bits is morethan 2 and the PUCCH resource includes an orthogonal cover code.

In an example, in order to transmit HARQ-ACK information on a PUCCHresource, a wireless device may determine the PUCCH resource from aPUCCH resource set. The PUCCH resource set may be determined asmentioned above. The wireless device may determine the PUCCH resourcebased on a PUCCH resource indicator field in a DCI (e.g., with a DCIformat 1_0 or DCI for 1_1) received on a PDCCH. A 3-bit PUCCH resourceindicator field in the DCI may indicate one of eight PUCCH resources inthe PUCCH resource set. The wireless device may transmit the HARQ-ACKinformation in a PUCCH resource indicated by the 3-bit PUCCH resourceindicator field in the DCI.

In an example, the wireless device may transmit one or more UCI bits viaa PUCCH resource of an active uplink BWP of a PCell or a PUCCH secondarycell. Since at most one active uplink BWP in a cell is supported for awireless device, the PUCCH resource indicated in the DCI is naturally aPUCCH resource on the active uplink BWP of the cell.

FIG. 27 shows example of multiple BWPs configuration. A gNB may transmitone or more messages comprising configuration parameters of one or morebandwidth parts (BWP) of a cell. The cell may be a PCell or a SCell. Theone or more messages may comprise: RRC connection reconfigurationmessage (e.g., RRCReconfiguration); RRC connection reestablishmentmessage (e.g., RRCRestablishment); and/or RRC connection setup message(e.g., RRCSetup). The one or more BWPs may have different numerologies.A gNB may transmit one or more control information for cross-BWPscheduling to a UE. One BWP may overlap with another BWP in frequencydomain.

In an example, a gNB may transmit one or more messages comprisingconfiguration parameters of one or more DL and/or UL BWPs for a cell,with at least one BWP as the active DL or UL BWP, and zero or one BWP asthe default DL or UL BWP. For the PCell, the active DL BWP may be the DLBWP on which the UE may monitor one or more PDCCH, and/or receive PDSCH.The active UL BWP is the UL BWP on which the UE may transmit uplinksignal. For a secondary cell (SCell) if configured, the active DL BWPmay be the DL BWP on which the UE may monitor one or more PDCCH andreceive PDSCH when the SCell is activated by receiving a MACactivation/deactivation CE. The active UL BWP is the UL BWP on which theUE may transmit PUCCH (if configured) and/or PUSCH when the SCell isactivated by receiving a MAC activation/deactivation CE. Configurationof multiple BWPs may be used to save UE's power consumption. Whenconfigured with an active BWP and a default BWP, a UE may switch to thedefault BWP if there is no activity on the active BWP. For example, adefault BWP may be configured with narrow bandwidth, an active BWP maybe configured with wide bandwidth. If there is no signal transmitting orreceiving, the UE may switch the BWP to the default BWP, which mayreduce power consumption.

In an example, for each DL BWP or UL BWP in a set of DL BWPs or UL BWPs,respectively, the wireless device may be configured the followingparameters for the serving cell: a subcarrier spacing provided by ahigher layer parameter (e.g., subcarrierSpacing); a cyclic prefixprovided by a higher layer parameter (e.g., cyclicPrefix); a first PRBand a number of contiguous PRBs indicated by a higher layer parameter(e.g., locationAndBandwidth) that is interpreted as RIV, and the firstPRB is a PRB offset relative to the PRB indicated by higher layerparameters (e.g., offsetToCarrier and subcarrierSpacing); an index inthe set of DL BWPs or UL BWPs by respective a higher layer parameter(e.g., bwp-Id); a set of BWP-common and a set of BWP-dedicatedparameters by higher layer parameters (e.g., bwp-Common andbwp-Dedicated).

In an example, switching BWP may be triggered by a DCI or a timer. Whena UE receives a DCI indicating DL BWP switching from an active BWP to anew BWP, the UE may monitor PDCCH and/or receive PDSCH on the new BWP.When the UE receives a DCI indicating UL BWP switching from an activeBWP to a new BWP, the UE may transmit PUCCH (if configured) and/or PUSCHon the new BWP. A gNB may transmit one or more messages comprising a BWPinactivity timer to a UE. The UE starts the timer when it switches itsactive DL BWP to a DL BWP other than the default DL BWP. The UE mayrestart the timer to the initial value when it successfully decodes aDCI to schedule PDSCH(s) in its active DL BWP. The UE may switch itsactive DL BWP to the default DL BWP when the BWP timer expires.

In an example, a BWP may be configured with: a subcarrier spacing, acyclic prefix, a number of contiguous PRBs, an offset of the first PRBin the number of contiguous PRBs relative to the first PRB, or Q controlresource sets if the BWP is a DL BWP.

In an example, on a SCell, there may be no initial active BWP since theinitial access is performed on the PCell. For example, the initiallyactivated DL BWP and/or UL BWP, when the SCell is activated, may beconfigured or reconfigured by RRC signaling. In an example, the defaultBWP of the SCell may also be configured or reconfigured by RRCsignaling.

In an example, gNB may configure UE-specific default DL BWP other thaninitial active BWP after RRC connection, e.g., for the purpose of loadbalancing. The default BWP may support other connected mode operations(besides operations supported by initial active BWP), e.g., fall backand/or connected mode paging. In this case, the default BWP may comprisecommon search space, e.g., at least a search space needed for monitoringa pre-emption indication.

In an example, a DL BWP other than the initial active DL BWP may beconfigured to a UE as the default DL BWP. The reconfiguring the defaultDL BWP may be due to load balancing and/or different numerologiesemployed for active DL BWP and initial active DL BWP.

In an example, for a paired spectrum, DL and UL BWPs may beindependently activated while, for an unpaired spectrum DL and UL BWPSare jointly activated. In case of bandwidth adaptation, where thebandwidth of the active downlink BWP may be changed, there may, in caseof an unpaired spectrum, be a joint activation of a new downlink BWP andnew uplink BWP. For example, a new DL/UL BWP pair where the bandwidth ofthe uplink BWPs may be the same (e.g., no change of uplink BWP).

In an example embodiment, making an association between DL BWP and ULBWP may allow that one activation/deactivation command may switch bothDL and UL BWPs at once. Otherwise, separate BWP switching commands maybe necessary.

In an example, PUCCH resources may be configured in a configured UL BWP,in a default UL BWP and/or in both. For instance, if the PUCCH resourcesare configured in the default UL BWP, UE may retune to the default ULBWP for transmitting an SR. for example, the PUCCH resources areconfigured per BWP or a BWP other than the default BWP, the UE maytransmit an SR in the current active BWP without retuning.

In an example, there may be at most one active DL BWP and at most oneactive UL BWP at a given time for a serving cell. A BWP of a cell may beconfigured with a specific numerology/TTI. In an example, a logicalchannel and/or logical channel group that triggers SR transmission whilethe wireless device operates in one active BWP, the corresponding SR mayremain triggered in response to BWP switching.

In an example, when a new BWP is activated, a configured downlinkassignment may be initialized (if not active) or re-initialized (ifalready active) using PDCCH. In an example, via one or more RRCmessages/signaling, a wireless device may be configured with at leastone UL BWP, at least one DL BWP, and one or more configured grants for acell. The one or more configured grants may be semi-persistentscheduling (SPS), Type 1 grant-free (GF) transmission/scheduling, and/orType 2 GF transmission/scheduling. In an example, one or more configuredgrants may be configured per UL BWP. For example, one or more radioresources associated with one or more configured grants may not bedefined/assigned/allocated across two or more UL BWPs.

In an example, an BWP may be in active during a period of time when aBWP inactivity timer is running. For example, a base station maytransmit a control message to a wireless device to configure a firsttimer value of an BWP inactivity timer. The first timer value maydetermine how long a BWP inactivity timer runs, e.g., a period of timethat a BWP inactivity timer runs. For example, the BWP inactivity timermay be implemented as a count-down timer from a first timer value downto a value (e.g., zero). In an example embodiment, the BWP inactivitytimer may be implemented as a count-up timer from a value (e.g., zero)up to a first timer value down. In an example embodiment, the BWPinactivity timer may be implemented as a down-counter from a first timervalue down to a value (e.g., zero). In an example embodiment, the BWPinactivity timer may be implemented as a count-up counter from a value(e.g., zero) up to a first timer value down. For example, a wirelessdevice may restart a BWP inactivity timer (e.g., UL BWP and/or DL BWPinactivity timers) when the wireless device receives (and/or decodes) aDCI to schedule PDSCH(s) in its active BWP (e.g., its active UL BWP, itsactive DL BWP, and/or UL/DL BWP pair).

FIG. 28 shows example of BWP switching mechanism. A UE may receive RRCmessage comprising parameters of a SCell and one or more BWPconfiguration associated with the SCell. Among the one or more BWPs, atleast one BWP may be configured as the first active BWP (e.g., BWP 1 inFIG. 28), one BWP as the default BWP (e.g., BWP 0 in FIG. 28). The UEmay receive a MAC CE to activate the SCell at the n^(th) slot. The UEmay start the sCellDeactivationTimer, and start CSI related actions forthe SCell, and/or start CSI related actions for the first active BWP ofthe SCell at the (n+x)^(th) slot. The UE may start the BWP inactivitytimer at the (n+x+k)^(th) slot in response to receiving a DCI indicatingswitching BWP from BWP 1 to BWP 2. When receiving a PDCCH indicating DLscheduling on BWP 2, for example, at the (n+x+k+m)^(th) slot, the UE mayrestart the BWP inactivity timer. The UE may switch back to the defaultBWP (e.g., BWP 0) as an active BWP when the BWP inactivity timerexpires, at the (n+x+k+m+l)^(th) slot. The UE may deactivate the SCellwhen the sCellDeactivationTimer expires.

In an example, a BWP inactivity timer may be applied in a PCell. A basestation may transmit one or more RRC messages comprising a BWPinactivity timer to a wireless device. The wireless device may start theBWP inactivity timer if the wireless devices switches its active DL BWPto a DL BWP other than the default DL BWP on the PCell. The wirelessdevice may restart the BWP inactivity timer if it successfully decodes aDCI to schedule PDSCH(s) in its active DL BWP. The wireless device mayswitch its active DL BWP to the default DL BWP if the BWP inactivitytimer expires.

In an example, employing the BWP inactivity timer may reduce UE's powerconsumption when the UE is configured with multiple BWPs on a cell (aPCell or a SCell). The UE may switch to a default BWP on the PCell orSCell when there is no activity on an active BWP (e.g., when the BWPinactivity timer expires).

In an example, a gNB may transmit one or more RRC message comprising oneor more CSI configuration parameters comprising at least: one or moreCSI-RS resource settings; one or more CSI reporting settings, and oneCSI measurement setting.

In an example, a CSI-RS resource setting may comprise one or more CSI-RSresource sets. In an example, there may be one CSI-RS resource set forperiodic CSI-RS, or semi-persistent (SP) CSI-RS. In an example, a CSI-RSresource set may comprise at least one of: one CSI-RS type (e.g.,periodic, aperiodic, or semi-persistent); one or more CSI-RS resourcescomprising at least one of: CSI-RS resource configuration identity (orindex); number of CSI-RS ports; CSI-RS configuration (symbol and RElocations in a subframe); CSI-RS subframe configuration (subframelocation, offset, and/or periodicity in radio frame); CSI-RS powerparameter; CSI-RS sequence parameter; CDM type parameter; frequencydensity; transmission comb; and/or QCL parameters.

In an example, one or more CSI-RS resources may be transmittedperiodically, using aperiodic transmission, using a multi-shottransmission, and/or using a SP transmission. In a periodictransmission, the configured CSI-RS resource may be transmitted using aconfigured periodicity in time domain. In an aperiodic transmission, theconfigured CSI-RS resource may be transmitted in a dedicated time slotor subframe. In a multi-shot or SP transmission, the configured CSI-RSresource may be transmitted within a configured period. In an example, agNB may transmit one or more SP CSI-RSs with a periodicity. The gNB maystop transmission of the one or more SP CSI-RSs if the CSI-RS isconfigured with a transmission duration. The gNB may stop transmissionof the one or SP CSI-RSs in response to transmitting a MAC CE or DCI fordeactivating (or stopping the transmission of) the one or more SPCSI-RSs.

In an example, a CSI reporting setting may comprise at least one of: onereport configuration identifier; one report type; one or more reportedCSI parameter(s); one or more CSI type (e.g., type I or type II); one ormore codebook configuration parameters; one or more parametersindicating time-domain behavior; frequency granularity for CQI and PMI;and/or measurement restriction configurations. The report type mayindicate a time domain behavior of the report (aperiodic, SP, orperiodic). The CSI reporting setting may further comprise at least oneof: one periodicity parameter; one duration parameter; and/or one offset(e.g., in unit of slots), if the report type is a periodic or SP report.The periodicity parameter may indicate a periodicity of a CSI report.The duration parameter may indicate a duration of CSI reporttransmission. The offset parameter may indicate value of timing offsetof CSI report.

In an example, a CSI measurement setting may comprise one or more linkscomprising one or more link parameters. The link parameter may compriseat least one of: one CSI reporting setting indication, CSI-RS resourcesetting indication, and one or more measurement parameters.

FIG. 29 shows example of various CSI report triggering mechanisms. In anexample, a gNB may trigger a CSI reporting by transmitting an RRCmessage, or a MAC CE, or a DCI, as shown in FIG. 29. In an example, a UEmay perform periodic CSI reporting (e.g., P-CSI reporting in FIG. 29)based on an RRC message and one or more periodic CSI-RSs. In an example,a UE may not be allowed (or required) to perform periodic CSI reportingbased on one or more aperiodic CSI-RSs and/or one or more SP CSI-RSs. Inan example, a UE may perform SP CSI reporting (e.g., SP-CSI reporting inFIG. 29) based on a MAC CE and/or a DCI and based on one or moreperiodic or SP CSI-RSs. In an example, a UE may not be allowed (orrequired) to perform SP CSI reporting based on one or more aperiodicCSI-RSs. In an example, a UE may perform aperiodic CSI reporting (e.g.,Ap-CSI reporting in FIG. 29) based on a DCI and based on one or moreperiodic, SP, or aperiodic CSI-RSs. In an example, a wireless device mayperform a SP CSI reporting on a PUCCH in response to the SP CSIreporting being activated (or triggered) by a MAC CE. The wirelessdevice may perform a SP CSI reporting on a PUSCH in response to the SPCSI reporting being activated (or triggered). In an example, a basestation may instruct (e.g., by transmitting the MAC CE) a wirelessdevice to perform SP CSI reporting on PUCCH when a compact CSI (e.g.,small amount of report contents) is required by the base station, or DCItransmission is not convenient for the base station, and/or the CSI isnot urgently required by the base station. In an example, a base stationmay instruct (e.g., by transmitting the DCI) a wireless device toperform SP CSI reporting on PUSCH when a large-sized CSI (e.g., bigamount of report contents) is required by the base station, or a DCItransmission is convenient for the base station, and/or the CSI isurgently required by the base station.

FIG. 30 shows an example of SP CSI reporting in a cell. In an example, abase station (e.g., gNB in FIG. 30) may transmit to a wireless device(e.g., UE in FIG. 30) one or more RRC messages comprising configurationparameters of one or more SP CSI reporting configurations. The basestation may transmit to the wireless device, at slot (or subframe) n, a1^(st) MAC CE or DCI indicating an activation of a SP CSI reportingconfiguration of the one or more SP CSI reporting configurations. Thebase station may start transmitting one or more SP CSI-RSs at slot (orsubframe) n+k. In an example, k may be zero or an integer greater thanzero, configured by an RRC message, or be predefined as a fixed value.

As shown in FIG. 30, after or in response to receiving the 1^(st) MAC CEor the 1^(st) DCI, the wireless device may perform CSI measurements onone or more CSI-RSs according to the activated SP CSI reportingconfiguration. In an example, after or in response to receiving the1^(st) MAC CE or the 1^(st) DCI, the wireless device may transmit one ormore SP CSI reports (e.g., based on the CSI measurements) atslot/subframe n+k+m, n+k+m+l, n+k+m+2*l, etc., with a periodicityof/subframes (or slots). The periodicity may be configured in an RRCmessage. In an example, the UE may receive a 2^(nd) MAC/DCI indicating adeactivation of the SP CSI reporting configuration. After receiving the2^(nd) MAC/DCI, or in response to the 2^(nd) MAC/DCI, the UE may stoptransmitting the one or more SP CSI reports. In an example, k may bezero (configured, or predefined). In an example, m (e.g., when k=0) maybe a time offset between the wireless device receives the 1^(st) MACCE/DCI for activation of the SP CSI reporting and the wireless devicetransmits a first SP CSI report of the one or more SP CSI reports. In anexample, m may be configured by an RRC message, or be predefined as afixed value. A value of m may depend on the capability of a UE and/orthe network.

As shown in FIG. 30, a wireless device may assume a CSI-RS transmissionperiod (e.g., CSI-RS transmission Window in FIG. 30), in response to a1^(st) MAC CE/DCI for activation of a SP CSI reporting configuration andbased on one or more configuration parameters of the activated SP CSIreporting configuration. The base station may transmit one or moreCSI-RSs at least in the CSI-RS transmission period, based on theactivated SP CSI reporting configuration. In an example, the wirelessdevice may perform CSI measurements on the one or more CSI-RSstransmitted in the CSI-RS transmission period.

In existing 3GPP technology specifications, when a UE activates theSCell, the UE may apply normal SCell operations including: SRStransmissions on the SCell; CQI/PMI/RI/PTI reporting for the SCell;PDCCH monitoring on the SCell; and/or PDCCH monitoring for the SCell. Ifthe SCell is deactivated, a UE may perform the following actions: nottransmit SRS on the S Cell; not report CQI/PMI/RI/PTI for the SCell; nottransmit on UL-SCH on the SCell; not transmit on RACH on the SCell; notmonitor the PDCCH on the SCell; not monitor the PDCCH for the SCell.When SCell is deactivated, the ongoing Random Access procedure on theSCell, if any, may be aborted.

In a NR system, a gNB may transmit PDCCH or PDSCH via one or more beamson a PCell, or one or more SCells. For example, a gNB may transmit afirst PDCCH or PDSCH on a PCell operating on a low carrier frequency(e.g., 2 GHz), and a second PDCCH or PDSCH via multiple beams on a SCelloperating on a high carrier frequency (e.g., 6 GHz, 30 GHz, or 70 GHz).In this case, the gNB may provide wide coverage by the PCell, and highdata rate by the SCell when necessary. In an example, a UE in the widecoverage of the PCell may frequently switch beam pair link with theSCell when moving around in the PCell, although there may be no beampair link change with the PCell. The UE may perform beam management onthe SCell to improve beam pair link quality with the SCell. The beamused on the PCell may be different from the beam on the SCell. Existingtechnologies may reuse a beam pair link of a PCell in a SCell whencommunicating with a UE on the SCell. A UE implementing existingtechnologies may not be able to determine when a beam report istransmitted for a SCell. Existing technologies may require a UE performbeam management for the S Cell even when the SCell is deactivated.Existing technologies may increase power consumption, data transmissiondelay caused by untimely beam pairing, channel quality report error.Example embodiments may improve power consumption when performing beammanagement for a SCell, reduce data transmission delay and reducechannel quality report error.

In an example, a base station and/or a UE may perform beam management.The beam management may comprise at least one of: the UE measuring oneor more RS resources; the UE reporting L1-RSRP (Reference SignalReceiving Power) associated with the one or more RS resources; the basestation transmitting a DCI indicating a beam which may correspond to theone or more RS resources with L1-RSRP report from the UE.

FIG. 31 shows an example embodiment of a beam management of a SCell. Inan example, a wireless device (e.g., UE in FIG. 31) may receive, from abase station (e.g., gNB in FIG. 31), at least one RRC message comprisingconfiguration parameters of a plurality of cells comprising a primarycell and at least one secondary cell (e.g., SCell in FIG. 31), wherein,the configuration parameters may comprise at least one of: a referencesignal (RS) resource setting; and/or a CSI reporting setting for L1-RSRPreporting. A L1-RSRP may indicate the receiving quality of a RStransmitted from a beam. The RS resource setting may comprise a set ofRS resources, each RS resource associated with a RS resourceconfiguration identifier and radio resource configuration (e.g., numberof ports; time and frequency resource allocation; frequency density;etc.). In an example, the RS may be a CSI-RS, and/or a SS/PBCH block. Inan example, the CSI report setting for L1-RSRP reporting may compriseparameters indicating at least one of: an indicator indicating whether agroup-based beam reporting is supported; a number indicating the numberof reported RS; a value indicating frequency granularity for CSI report;parameters indicating periodicity; slot offset of CSI report; and/or aPUCCH resource for the L1-RSRP reporting. In an example, a RS resourcemay be transmitted with a beam direction. Different RS resources maytransmit with different beam direction.

In an example, the at least RRC message may further comprise a reportconfiguration type (e.g., indicating the time domain behavior of thereport—either aperiodic, semi-persistent, or periodic), if a gNB and/ora UE supports aperiodic, SP, or periodic L1-RSRP reporting.

In an example, as shown in FIG. 31, the gNB may transmit to the UE, amedia access control (MAC) command indicating activation of at least afirst SCell (e.g., the SCell in FIG. 31) in the at least one secondarycell. The UE may receive the MAC CE, and attempt to activate the atleast first SCell, by measuring one or more RS resources of the at leastfirst SCell.

In an example, the UE may not successfully activate the at least firstSCell, for example, failing detecting the one or more RS resource of theat least first SCell. Implementing existing technologies, the gNB maynot be aware of the UE's failure of activating the at least first SCell,if the UE doesn't signal the gNB about beam quality. Implementing theexisting technologies may cause transmission error if the gNB transmitdata on the unsuccessfully activated at least first SCell. A UE byimplementing example embodiments may feedback one or more information ofbeam management reports to the gNB indicating whether the activation issuccessful, before the gNB transmits data on the at least first SCell.

In an example, in response to receiving the MAC CE, a UE may measureRSRP of one or more RS associated with the at least first SCell. TheRSRP value may be defined by a 7-bit value in a range of [−140, −44] dbmwith 1 dB step size. In an example, the UE may determine the RSRP reportby some criterial. In an example, the RSRP report may be the best RSRPmeasurement among the set of RS resources configured by the RRC message.In an example, the RSRP report may be based on an averaged value overthe set of RS resources. In an example, the RSRP report may be based onan averaged value over one or more RS resources having RSRP greater thana threshold. In an example, the RSRP report may be based on an averagedvalue over a number of one or more RS resources having best RSRPmeasurement, wherein the number may be a configured valued by an RRCmessage, or a fixed value.

In an example, the UE may transmit the RSRP report on a PUCCH. The PUCCHmay be indicated by the RRC message, and/or transmitted on a PCell,pScell, or a PUCCH SCell. In an example, the UE may transmit the RSRPreport on a PUSCH. The PUSCH may be indicated by the RRC message, or aMAC CE, or a DCI.

In an example, the RSRP report may comprise at least one of: a RSRPvalue; and/or a RS resource indicator. The RS resource indicator mayindicate a RS resource having the best L1-RSRP measurement among the setof RS resource configured by the RRC message. In an example, the RSresource indicator may indicate a RS resource have a L1-RSRP measurementgreater than a threshold. The threshold may be a predefined value, or avalue configured by an RRC message. The RSRP value may be a L1-RSRPmeasurement having a 7-bit value with a range of [−140, −44] dbm, basedon the RS resource associated with the RS resource indicator.

In an example, if the number indicating the number of reported RS in theRRC message indicates more than one RS are reported with L1-RSRP, a UEmay transmit the RSRP report for more than one RS. In an example, theRSRP report may comprise at least one of: a first RSRP value; and/or asecond RSRP value. The first RSRP value may correspond to a first RShaving the best L1-RSRP measurement result. The first RSRP value may aL1-RSRP having a 4-bit value. The second RSRP value may be a differenceof L1-RSRP value between the first RS and a at least second RS.

In an example, the at least second RS may have the second best RSRPvalue among the set of RS resources configured by the RRC message.

In an example, the at least second RS may be the RSs, except the firstRS in the set of RSs configured by the RRC message. In this case, thesecond RSRP value may be the difference of RSRP value of the first RSand averaged RSRP value of the at least second RS.

In an example, the at least second RS may be the RSs, except the firstRS, each RS having a RSRP greater than a threshold. In this case, thesecond RSRP value may be the difference of RSRP value of the first RSand averaged RSRP value of the at least second RS.

In an example, the at least second RS may be the RSs, except of thefirst RS, wherein, the number of the RSs may be a configured value, or apredefined value, and the RSs may have best RSRPs (except the first RS)among the set of RSs. In this case, the second RSRP value may be thedifference of RSRP value of the first RS and averaged RSRP value of theat least second RS.

In an example, the at least second RS may be indicated by an RRCmessage.

As shown in FIG. 31, the UE may receive the MAC CE for activation of afirst S Cell at subframe (or slot) n, the UE may start or restart aSCellDeactivationTimer in the same subframe (or slot) or a differentsubframe (or slot). In response to receiving the MAC CE, the UE maystart a beam report related action for the activated S Cell at subframe(or slot) n+k. The beam report may comprise at least one or more L1-RSRPvalue based on one or more RS resources. The value “k” may be configuredby an RRC message. In an example, the value “k” may be a predefinedvalue. In an example, in response to receiving the beam report, a gNBmay transmit one or more signal to the UE indicating a transmissionbeam. The transmission beam may be the beam associated with the RSRPreport. The one or more signal may be a DCI via PDCCH, or a controlinformation via PDSCH.

In existing technologies, a UE may transmit CQI/PMI/RI/CRI to a gNBindicating whether activation of a SCell is successful. In an example,when the SCell configured with multiple beams, the UE may not havecorrect CQI/PMI/RI/CRI measurements before the UE tunes its receivingbeam to a transmission beam of the gNB. Only when the UE tunes to thegNB's transmission beam, the UE may receive some control informationtransmitted from the transmission beam, and the UE may start to measureCQI/PMI/RI/CRI. Therefore, there is a need to transmit the one or moreL1-RSRP to indicate whether the activation of the SCell is successful,when the SCell is configured with multiple beams. In an example, asshown in FIG. 31, the UE, after receiving the MAC CE activating theSCell, may transmit one or more L1-RSRP report for the SCell, in a beammanagement procedure, wherein the one or more L1-RSRP may indicate thesignal quality (e.g., received power) of one or more beams associatedwith one or more RS resource. A UE may generate one or moreCQI/PMI/RI/CRI report in a CSI procedure. L1-RSRP may indicate a coarsechannel quality of a RS transmitted from a beam, while, CQI/PMI/RI/CRIreport may indicate a quantity of spatial property of channel from a gNBto the UE. A gNB may adjust a beam direction or change to another beambased on a L1-RSRP report. A gNB may determine a transmission format(e.g., MCS, resource allocation of PDCCH/PDSCH, MIMO transmissionformat, etc.) based on a CQI/PMI/RI/CRI. Example embodiment may improvedata transmission latency for a SCell when the SCell is configured withmultiple beams. Example embodiment may improve power consumption ofchannel state information reporting.

FIG. 32 shows an example embodiment of a beam management of a SCell. Inan example, a base station (e.g., gNB in FIG. 32) may transmit to awireless device (e.g., UE in FIG. 32), a MAC CE indicating deactivationof at least a first SCell (e.g., SCell in FIG. 32) in the at least onesecondary cells. In an example, the UE may deactivate at least a firstSCell by a SCellDeactivationTimer expiring. In response to deactivationof the at least first S Cell, the UE may stop transmission of one ormore beam report for the at least first SCell, wherein, the one or morebeam report may comprise at least a L1-RSRP associated with at least oneRS.

As shown in FIG. 32, the UE may receive a MAC CE for deactivation of aSCell at subframe (or slot) n, the UE may stop a beam report for thedeactivated SCell at subframe (or slot) n+k. The value “k” may beconfigured by an RRC message. In an example, the value “k” may be apredefined value. Example embodiment may improve power consumption ofchannel state information reporting when a SCell is deactivated. Exampleembodiment may improve uplink interference when performing beammanagement for a deactivated SCell.

In an example, a wireless device may receive from a base station, atleast one message comprising configuration parameters of a plurality ofcells comprising a primary cell and at least one secondary cell,wherein, the configuration parameters comprise at least radio resourceconfiguration of one or more reference signals. The wireless device mayreceive a media access control (MAC) command indicating activation of atleast a first SCell in the at least one secondary cell. The wirelessdevice may transmit one or more beam report for the at least first SCellin response to receiving the MAC command, wherein, the one or more beamreport comprising one or more reference signal received power (RSRP) ofat least one of the one or more reference signals for the at least firstSCell. In an example, the one or more reference signals comprise atleast one of: CSI-RS; and/or SS/PBCH blocks.

FIG. 33 shows an example embodiment of beam management and channel stateinformation report. In an example, a wireless device (e.g., UE in FIG.33) may receive, from a base station (e.g., gNB in FIG. 33), at leastone RRC message comprising configuration parameters of a plurality ofcells comprising a primary cell and at least one secondary cell (e.g.,SCell in FIG. 33), wherein, the configuration parameters may comprise atleast one of: a reference signal (RS) resource setting; and/or a CSIreporting setting for L1-RSRP reporting. A L1-RSRP may indicate thereceiving quality of a RS transmitted from a beam. The RS resourcesetting may comprise a set of RS resources, each RS resource associatedwith a RS resource configuration identifier and radio resourceconfiguration (e.g., number of ports; time and frequency resourceallocation; frequency density; etc.). In an example, the RS may be aCSI-RS, and/or a SS/PBCH block. In an example, the CSI report settingfor L1-RSRP reporting may comprise parameters indicating at least oneof: an indicator indicating whether a group-based beam reporting issupported; a number indicating the number of reported RS; a valueindicating frequency granularity for CSI report; parameters indicatingperiodicity; slot offset of CSI report; and/or a PUCCH resource for theL1-RSRP reporting. In an example, a RS resource may be transmitted witha beam direction. Different RS resources may transmit with differentbeam direction.

In an example, the at least RRC message may further comprise a reportconfiguration type (e.g., indicating the time domain behavior of thereport—either aperiodic, semi-persistent, or periodic), if a gNB and/ora UE supports aperiodic, SP, or periodic L1-RSRP reporting.

As shown in FIG. 33, the UE may receive a MAC CE for activation of afirst SCell at subframe (or slot) n, the UE may start or restart aSCellDeactivationTimer in the same subframe (or slot) or a differentsubframe (or slot). In an example, in response to receiving the MAC CE,the UE may start an invalid beam report for the activated SCell atsubframe (or slot) n+k. The invalid beam report may comprise at leastone or more L1-RSRP value based on one or more RS resources, lower thana predefined threshold, or a configured threshold. The value k (e.g., aninteger >=0) may be configured by an RRC message, depending on at leastcapability of the UE, and/or the gNB. In an example, the value k (e.g.,an integer >=0) may be a predefined value.

As shown in FIG. 33, The UE may start a valid beam report for theactivated SCell at subframe (or slot) n+k+m. The value m (e.g., aninteger >=0) may be configured by an RRC message, e.g., depending on atleast capability of the UE, and/or the gNB. In an example, the value m(e.g., an integer >=0) may be a predefined value. The valid beam reportmay be a L1-RSRP value measured on one or more RS resources, greaterthan the predefined threshold, or the configured threshold. In responseto the UE transmitting the valid beam report, the UE may finish settingup a beam pair link by tuning receiving beam to a transmission beam fromthe gNB.

In an example, the UE may start measuring CQI/PMI/RI/CRI on the beampair link. As shown in FIG. 33, the UE may start transmitting one ormore CQI/PMI/RI/CRI via a PUCCH at subframe (or slot) n+k+m+l. The valuel (e.g., an integer >=0) may be configured by an RRC message, e.g.,depending on at least capability of the UE, and/or the gNB. In anexample, the value l (e.g., an integer >=0) may be a predefined value.Example embodiments may provide mechanisms to improve power consumptionwhen perform channel state information for an activated SCell.

In an example, a UE may skip transmitting invalid beam report for theactivated S Cell, if the UE is capable of quick tuning its transceiverparameters. Example embodiments may improve power consumption and datatransmission latency when performing SCell activation.

FIG. 34 shows an example embodiment of beam management and channel stateinformation reporting for a SCell. In an example, a wireless device(e.g., UE in FIG. 34) may receive, from a base station (e.g., gNB inFIG. 34), at least one RRC message comprising configuration parametersof a plurality of cells comprising a primary cell and at least onesecondary cell (e.g., SCell in FIG. 34), wherein, the configurationparameters may comprise at least one of: a reference signal (RS)resource setting; and/or a CSI reporting setting for L1-RSRP reporting.A L1-RSRP may indicate the receiving quality of a RS transmitted from abeam. The RS resource setting may comprise a set of RS resources, eachRS resource associated with a RS resource configuration identifier andradio resource configuration (e.g., number of ports; time and frequencyresource allocation; frequency density; etc.). In an example, the RS maybe a CSI-RS, and/or a SS/PBCH block. In an example, the CSI reportsetting for L1-RSRP reporting may comprise parameters indicating atleast one of: an indicator indicating whether a group-based beamreporting is supported; a number indicating the number of reported RS; avalue indicating frequency granularity for CSI report; parametersindicating periodicity; slot offset of CSI report; and/or a PUCCHresource for the L1-RSRP reporting. In an example, a RS resource may betransmitted with a beam direction. Different RS resources may transmitwith different beam direction.

In an example, the at least RRC message may further comprise a reportconfiguration type (e.g., indicating the time domain behavior of thereport—either aperiodic, semi-persistent, or periodic), if a gNB and/ora UE supports aperiodic, SP, or periodic L1-RSRP reporting. As shown inFIG. 34, the UE may receive a MAC CE for activation of a first SCell atsubframe (or slot) n, the UE may start or restart aSCellDeactivationTimer in the same subframe (or slot) or a differentsubframe (or slot).

As shown in FIG. 34, the UE may start transmitting valid beam report atsubframe n+k. The value k (e.g., an integer >=0) may be configured by anRRC message, depending on at least capability of the UE, and/or the gNB.In an example, the value k (e.g., an integer >=0) may be a predefinedvalue. In response to the UE transmitting the valid beam report, the UEmay finish setting up a beam pair link by tuning receiving beam to atransmission beam from the gNB. In an example, the UE may startmeasuring CQI/PMI/RI/CRI on the beam pair link. The UE may starttransmitting one or more CQI/PMI/RI/CRI via a PUCCH at subframe (orslot) n+k+m. The value m (e.g., an integer >=0) may be configured by anRRC message, e.g., depending on at least capability of the UE, and/orthe gNB. In an example, the value m (e.g., an integer >=0) may be apredefined value.

In an example, when activating a SCell, a gNB may expect to getconfirmation of successful activation of the SCell by receiving validCQI report from a UE within a time period. For example, if the gNB doesnot receive a valid CQI report with the time period, the gNB may realizethat the activation of the SCell may be not successful, and the gNB maytry to activate another S Cell, or repeat the SCell activation process.It's necessary to define the time period a UE may transmit a valid CQI.

FIG. 35 shows an example embodiment of beam management and channel stateinformation report for a SCell. In an example, a wireless device (e.g.,UE in FIG. 35) may receive, from a base station (e.g., gNB in FIG. 35),at least one RRC message comprising configuration parameters of aplurality of cells comprising a primary cell and at least one secondarycell (e.g., SCell in FIG. 35), wherein, the configuration parameters maycomprise at least one of: a reference signal (RS) resource setting;and/or a CSI reporting setting for L1-RSRP reporting. A L1-RSRP mayindicate the receiving quality of a RS transmitted from a beam. The RSresource setting may comprise a set of RS resources, each RS resourceassociated with a RS resource configuration identifier and radioresource configuration (e.g., number of ports; time and frequencyresource allocation; frequency density; etc.). In an example, the RS maybe a CSI-RS, and/or a SS/PBCH block. In an example, the CSI reportsetting for L1-RSRP reporting may comprise parameters indicating atleast one of: an indicator indicating whether a group-based beamreporting is supported; a number indicating the number of reported RS; avalue indicating frequency granularity for CSI report; parametersindicating periodicity; slot offset of CSI report; and/or a PUCCHresource for the L1-RSRP reporting. In an example, a RS resource may betransmitted with a beam direction. Different RS resources may transmitwith different beam direction.

In an example, the at least RRC message may further comprise a reportconfiguration type (e.g., indicating the time domain behavior of thereport—either aperiodic, semi-persistent, or periodic), if a gNB and/ora UE supports aperiodic, SP, or periodic L1-RSRP reporting. As shown inFIG. 35, the UE may receive a MAC CE for activation of a first SCell atsubframe (or slot) n, the UE may start or restart aSCellDeactivationTimer in the same subframe (or slot) or a differentsubframe (or slot). In an example, in response to receiving the MAC CE,the UE may start an invalid beam report for the activated SCell atsubframe (or slot) n+k. The invalid beam report may comprise at leastone or more L1-RSRP value based on one or more RS resources, lower thana predefined threshold, or a configured threshold. The value k (e.g., aninteger >=0) may be configured by an RRC message, depending on at leastcapability of the UE, and/or the gNB. In an example, the value k (e.g.,an integer >=0) may be a predefined value.

As shown in FIG. 35, The UE may start a valid beam report for theactivated SCell at subframe (or slot) n+k+m. The value m (e.g., aninteger >=0) may be configured by an RRC message, e.g., depending on atleast capability of the UE, and/or the gNB. In an example, the value m(e.g., an integer >=0) may be a predefined value. The valid beam reportmay be a L1-RSRP value measured on one or more RS resources, greaterthan the predefined threshold, or the configured threshold. In responseto the UE transmitting the valid beam report, the UE may finish settingup a beam pair link by tuning receiving beam to a transmission beam fromthe gNB.

As shown in FIG. 35, the UE may start transmitting invalid CQI reportfor the SCell at subframe n+k+m+1, in response to transmitting validbeam report at subframe n+k+m. The value m (e.g., an integer >=0) and/orl (e.g., an integer >=0) may be configured by an RRC message. In anexample, the value m and/or l may be a predefined value. The UE maystart transmission of a valid CQI report for the S Cell at subframen+k+m+l+o. The value o (e.g., an integer >=0) may be configured by anRRC message, depending on at least capability of the UE, and/or the gNB.In an example, the value o (e.g., an integer >=0) may be a predefinedvalue. In an example, the valid CSI report may be an CSI valuecorrespond to a value other than CQI index=0 (out of range) in a CQItable. In an example, the invalid CSI report may be an CQI valuecorrespond to CQI index=0 (out of range) in the CQI table.

In an example, a UE may skip transmitting invalid beam report and/orinvalid CQI report for the activated S Cell. The UE may skiptransmitting invalid beam report and/or invalid CQI report, if the UE iscapable of quick tuning its transceiver parameters.

FIG. 36 shows an example embodiment of beam management and channel stateinformation report for a SCell. In an example, a wireless device (e.g.,UE in FIG. 36) may receive, from a base station (e.g., gNB in FIG. 36),at least one RRC message comprising configuration parameters of aplurality of cells comprising a primary cell and at least one secondarycell (e.g., SCell in FIG. 36), wherein, the configuration parameters maycomprise at least one of: a reference signal (RS) resource setting;and/or a CSI reporting setting for L1-RSRP reporting. A L1-RSRP mayindicate the receiving quality of a RS transmitted from a beam. The RSresource setting may comprise a set of RS resources, each RS resourceassociated with a RS resource configuration identifier and radioresource configuration (e.g., number of ports; time and frequencyresource allocation; frequency density; etc.). In an example, the RS maybe a CSI-RS, and/or a SS/PBCH block. In an example, the CSI reportsetting for L1-RSRP reporting may comprise parameters indicating atleast one of: an indicator indicating whether a group-based beamreporting is supported; a number indicating the number of reported RS; avalue indicating frequency granularity for CSI report; parametersindicating periodicity; slot offset of CSI report; and/or a PUCCHresource for the L1-RSRP reporting. In an example, a RS resource may betransmitted with a beam direction. Different RS resources may transmitwith different beam direction.

In an example, the at least RRC message may further comprise a reportconfiguration type (e.g., indicating the time domain behavior of thereport—either aperiodic, semi-persistent, or periodic), if a gNB and/ora UE supports aperiodic, SP, or periodic L1-RSRP reporting. As shown inFIG. 35, the UE may receive a MAC CE for activation of a first SCell atsubframe (or slot) n, the UE may start or restart aSCellDeactivationTimer in the same subframe (or slot) or a differentsubframe (or slot). In an example, in response to receiving the MAC CE,the UE may start an invalid beam report for the activated SCell atsubframe (or slot) n+k. The invalid beam report may comprise at leastone or more L1-RSRP value based on one or more RS resources, lower thana predefined threshold, or a configured threshold. The value k (e.g., aninteger >=0) may be configured by an RRC message, depending on at leastcapability of the UE, and/or the gNB. In an example, the value k (e.g.,an integer >=0) may be a predefined value.

As shown in FIG. 36, The UE may start a valid beam report for theactivated SCell at subframe (or slot) n+k+m. The value m (e.g., aninteger >=0) may be configured by an RRC message, e.g., depending on atleast capability of the UE, and/or the gNB. In an example, the value m(e.g., an integer >=0) may be a predefined value. The valid beam reportmay be a L1-RSRP value measured on one or more RS resources, greaterthan the predefined threshold, or the configured threshold. In responseto the UE transmitting the valid beam report, the UE may finish settingup a beam pair link by tuning receiving beam to a transmission beam fromthe gNB.

As shown in FIG. 36, the UE may start transmitting valid CQI report forthe SCell at subframe n+k+m+l, in response to transmitting valid beamreport at subframe n+k+m.

FIG. 37 shows an example embodiment of beam management and channel stateinformation report for a SCell. In an example, a wireless device (e.g.,UE in FIG. 37) may receive, from a base station (e.g., gNB in FIG. 37),at least one RRC message comprising configuration parameters of aplurality of cells comprising a primary cell and at least one secondarycell (e.g., SCell in FIG. 37), wherein, the configuration parameters maycomprise at least one of: a reference signal (RS) resource setting;and/or a CSI reporting setting for L1-RSRP reporting. A L1-RSRP mayindicate the receiving quality of a RS transmitted from a beam. The RSresource setting may comprise a set of RS resources, each RS resourceassociated with a RS resource configuration identifier and radioresource configuration (e.g., number of ports; time and frequencyresource allocation; frequency density; etc.). In an example, the RS maybe a CSI-RS, and/or a SS/PBCH block. In an example, the CSI reportsetting for L1-RSRP reporting may comprise parameters indicating atleast one of: an indicator indicating whether a group-based beamreporting is supported; a number indicating the number of reported RS; avalue indicating frequency granularity for CSI report; parametersindicating periodicity; slot offset of CSI report; and/or a PUCCHresource for the L1-RSRP reporting. In an example, a RS resource may betransmitted with a beam direction. Different RS resources may transmitwith different beam direction.

In an example, the at least RRC message may further comprise a reportconfiguration type (e.g., indicating the time domain behavior of thereport—either aperiodic, semi-persistent, or periodic), if a gNB and/ora UE supports aperiodic, SP, or periodic L1-RSRP reporting. As shown inFIG. 34, the UE may receive a MAC CE for activation of a first SCell atsubframe (or slot) n, the UE may start or restart aSCellDeactivationTimer in the same subframe (or slot) or a differentsubframe (or slot).

As shown in FIG. 37, the UE may start transmitting valid beam report atsubframe n+k. The value k (e.g., an integer >=0) may be configured by anRRC message, depending on at least capability of the UE, and/or the gNB.In an example, the value k (e.g., an integer >=0) may be a predefinedvalue. In response to the UE transmitting the valid beam report, the UEmay finish setting up a beam pair link by tuning receiving beam to atransmission beam from the gNB.

As shown in FIG. 37, the UE may start transmitting valid CQI report forthe SCell at subframe n+k+m, in response to transmitting valid beamreport at subframe n+k. In an example, m may be zero when the UE iscapable of quick tuning its transceiver parameter and measuring L1-RSRPand CQI.

Example embodiments may improve power consumption of channel stateinformation report for a SCell when the SCell is activated, for example,by defining timing of beam management and CQI/PMI/RI/CRI report for aSCell. Example embodiment may reduce data transmission latency on theSCell.

In an example, a wireless device may receive, from a base station, atleast one message comprising configuration parameters of a plurality ofcells comprising a primary cell and at least one secondary cell,wherein, the configuration parameters comprise at least radio resourceconfiguration of one or more reference signals (e.g., SS blocks, and/orCSI-RS). In an example, the wireless device may receive a media accesscontrol (MAC) command indicating activation of at least a first SCell inthe at least one secondary cell. The wireless may transmit one or morebeam report for the at least first SCell, in response to receiving theMAC command. In an example, the one or more beam report may comprise oneor more reference signal received power (RSRP) of at least one of theone or more reference signals for the at least first cell. The wirelessdevice may transmit one or more CSI report for the at least first cell,in response to transmitting a valid beam report, wherein, the valid beamreport comprises at least one or more RSRP with value greater than athreshold. The threshold may be a configured value, or be a predefinedvalue. In an example, the one or more CSI report may comprise at leastone of: CQI; RI; PMI; or CRI. In an example, the wireless device maytransmit one or more invalid CSI report for the at least first SCell, ata first subframe (or slot) which is n subframes after the wirelessdevice transmit the valid beam report. n may be an integer (>=0). In anexample, the wireless device may transmit one or more valid CSI reportfor the at least first SCell, at a third subframe (or slot) which is msubframes after the wireless device transmit the valid beam report. Inan example, m may be an integer (>=0). In an example, m may be greaterthan, or equal to, n. In an example, the valid CSI report may be an CQIvalue correspond to a value other than CQI index=0 (out of range) in aCQI table. In an example, the invalid CSI report may be an CSI valuecorrespond to CQI index=0 (out of range) in the CQI table.

According to various embodiments, a device such as, for example, awireless device, off-network wireless device, a base station, a corenetwork device, and/or the like, may comprise one or more processors andmemory. The memory may store instructions that, when executed by the oneor more processors, cause the device to perform a series of actions.Embodiments of example actions are illustrated in the accompanyingfigures and specification. Features from various embodiments may becombined to create yet further embodiments.

FIG. 38 is a flow diagram of an aspect of an embodiment of the presentdisclosure. At 3810, a wireless device may receive one or more messagesfrom a base station. The one or more messages may comprise configurationparameters of a layer 1 reference signal received power reporting for asecondary cell. The configuration parameters may indicate resourceconfigurations of a plurality of reference signals on the secondarycell. At 3820, a medium access control control element may be received.The medium access control control element may indicate activation of thesecondary cell. At 3830, a layer 1 reference signal received powerreport for the layer 1 reference signal received power reporting for thesecondary cell may be transmitted in response to the medium accesscontrol control element. The layer 1 reference signal received powerreport may comprise first fields indicating at least one referencesignal of the plurality of reference signals. The layer 1 referencesignal received power report may comprise second fields indicating atleast a layer 1 reference signal received power value of the at leastone reference signals.

According to an example embodiment, a second medium access controlcontrol element indicating deactivation of the secondary cell may bereceived. The transmitting the layer 1 reference signal received powerreport for the secondary cell may be stopped in response to the secondmedium access control control element. According to an exampleembodiment, a second power value of the at least the layer 1 referencesignal received power value may be a 4-bit value indicating a powervalue relative to a first power value of the at least the layer 1reference signal received power value.

According to an example embodiment, a first power value of the at leastthe layer 1 reference signal received power value may be a 7-bit value.According to an example embodiment, the 7-bit value may indicate a powervalue between −140 dbm and −44 dbm.

According to an example embodiment, a channel quality indicator reportfor the secondary cell may be transmitted in response to the mediumaccess control control element. According to an example embodiment, thechannel quality indicator report may comprise a channel qualityindicator. The channel quality indicator report may comprise a precodingmatrix indicator. The channel quality indicator report may comprise achannel state information reference signal resource indicator. Thechannel quality indicator report may comprise a synchronizationsignal/physical broadcast channel block resource indicator. The channelquality indicator report may comprise a layer indicator.

According to an example embodiment, the wireless device may transmit thelayer 1 reference signal received power report from a first slot anumber of slots after a second slot when the wireless device receivesthe medium access control control element. According to an exampleembodiment, the number of slots may be a configured value or apredefined value. According to an example embodiment, the wirelessdevice may transmit the layer 1 reference signal received power reportwith a report periodicity. According to an example embodiment, thereport periodicity may indicate the one or more messages. According toan example embodiment, the at least the layer 1 reference signalreceived power value may be equal to or greater than a threshold.According to an example embodiment, the threshold may be indicated in aradio resource control message. According to an example embodiment, achannel quality indicator report for the secondary cell may betransmitted in response to a power value of the at least the layer 1reference signal received power value being equal to or greater than athreshold.

According to an example embodiment, a plurality of reference signals maycomprise a first plurality of channel state information referencesignals. The plurality of reference signals may comprise a secondplurality of synchronization signal blocks. According to an exampleembodiment, the first plurality of channel state information referencesignals may comprise one or more periodic channel state informationreference signals. According to an example embodiment, a transmissionperiodicity of the one or more periodic channel state informationreference signals may be indicated in the one or more messages.According to an example embodiment, the configuration parameters maycomprise resource configurations of an uplink control channel for thelayer 1 reference signal received power reporting for the secondarycell. According to an example embodiment, the wireless device maytransmit the layer 1 reference signal received power report via theuplink control channel. According to an example embodiment, the uplinkcontrol channel may be configured on a primary cell, or a physicaluplink control channel secondary cell.

FIG. 39 is a flow diagram of an aspect of an embodiment of the presentdisclosure. At 3910, a wireless device may receive one or more messagesfrom a base station. The one or more messages may comprise firstconfiguration parameters of a layer 1 reference signal received powerreport for a secondary cell. The one or more messages may comprisesecond configuration parameters of a channel quality indicator reportfor the secondary cell. At 3920, a medium access control control elementmay be received at a first slot. The medium access control controlelement may indicate activation of the secondary cell. At 3930, thelayer 1 reference signal received power report may be transmitted, at asecond slot occurring a number of slots after the first slot, the layer1 reference signal received power report, in response to the mediumaccess control control element. At 3940, a channel quality indictorreport for the secondary cell may be transmitted at a third slot inresponse to a reference signal received power value of the layer 1reference signal received power report being greater than a threshold.

According to an example embodiment, the wireless device may transmit thelayer 1 reference signal received power report via radio resource of anuplink control channel According to an example embodiment, the thresholdmay be configured in a radio resource control message. According to anexample embodiment, the number of slots may be configured in a radioresource control message. According to an example embodiment, the numberof slots may be a predefined value. According to an example embodiment,the third slot may occur a second number of slots after the second slot.According to an example embodiment, the channel quality indictor reportmay comprise an invalid value of channel quality indicator. The invalidvalue may be below a second threshold. According to an exampleembodiment, the channel quality indicator report may comprise a validvalue of channel quality indicator. The valid value may be greater thana second threshold. According to an example embodiment, a downlinkcontrol channel may be monitored for downlink assignment or uplink grantafter transmitting the channel quality indicator report. According to anexample embodiment, a second MAC CE indicating deactivation of thesecondary cell may be received. The transmitting the layer 1 referencesignal received power report and/or the channel quality indicator reportmay be stopped in response to the second MAC CE. According to an exampleembodiment, the one or more messages may comprise configurationparameters of a plurality of cells comprising a primary cell and thesecondary cell. According to an example embodiment, the wireless devicemay transmit the layer 1 reference signal received power report based onthe first configuration parameters. According to an example embodiment,the wireless device may transmit the channel quality indicator reportbased on the second configuration parameters.

According to an example embodiment, the first configuration parametersmay comprise radio resources of one or more reference signals comprisingchannel state information reference signals and/or synchronizationsignal blocks. The first configuration parameters may comprise a numberof reported reference signals in the layer 1 reference signal receivedpower report. The first configuration parameters may comprise a reportperiodicity of the layer 1 reference signal received power report. Thefirst configuration parameters may comprise radio resources of an uplinkcontrol channel for the layer 1 reference signal received power report.According to an example embodiment, the wireless device may transmit thelayer 1 reference signal received power report with the reportperiodicity of the layer 1 reference signal received power report.According to an example embodiment, the wireless device may transmit thechannel quality indicator report with the report periodicity of thechannel quality indicator report. According to an example embodiment,the wireless device may transmit the layer 1 reference signal receivedpower report via radio resources of the uplink control channel for thelayer 1 reference signal received power report.

According to an example embodiment, the second configuration parametersmay comprise radio resource configuration of one or more referencesignals comprising channel state information reference signals and/orsynchronization signal blocks. The second configuration parameters maycomprise a channel station information report type. The secondconfiguration parameters may comprise parameters of codebookconfigurations. The second configuration parameters may comprisefrequency granularity parameters. The second configuration parametersmay comprise a report periodicity of the channel quality indicatorreport. The second configuration parameters may comprise measurementrestriction configuration parameters. The second configurationparameters may comprise radio resource configuration of uplink controlchannel for the channel quality indicator report. According to anexample embodiment, the layer 1 reference signal received power reportmay comprise one or more reference signal resource index indicating oneor more reference signals of a plurality of reference signals. The layer1 reference signal received power report may comprise one or more layer1 reference signal received power values for the one or more referencesignals. the layer 1 reference signal received power report may comprisea first value of the one or more layer 1 reference signal received powervalues may be a biggest layer 1 reference signal received power valueamong layer 1-reference signal received power values of the plurality ofreference signals.

In this disclosure, “a” and “an” and similar phrases are to beinterpreted as “at least one” or “one or more.” Similarly, any term thatends with the suffix “(s)” is to be interpreted as “at least one” or“one or more.” In this disclosure, the term “may” is to be interpretedas “may, for example.” In other words, the term “may” is indicative thatthe phrase following the term “may” is an example of one of a multitudeof suitable possibilities that may, or may not, be employed to one ormore of the various embodiments. If A and B are sets and every elementof A is also an element of B, A is called a subset of B. In thisspecification, only non-empty sets and subsets are considered. Forexample, possible subsets of B={cell1, cell2} are: {cell1}, {cell2}, and{cell1, cell2}. The phrase “based on” is indicative that the phrasefollowing the term “based on” is an example of one of a multitude ofsuitable possibilities that may, or may not, be employed to one or moreof the various embodiments. The phrase “in response to” is indicativethat the phrase following the phrase “in response to” is an example ofone of a multitude of suitable possibilities that may, or may not, beemployed to one or more of the various embodiments. The terms“including” and “comprising” should be interpreted as meaning“including, but not limited to.”

In this disclosure and the claims, differentiating terms like “first,”“second,” “third,” identify separate elements without implying anordering of the elements or functionality of the elements.Differentiating terms may be replaced with other differentiating termswhen describing an embodiment.

In this disclosure, various embodiments are disclosed. Limitations,features, and/or elements from the disclosed example embodiments may becombined to create further embodiments within the scope of thedisclosure.

In this disclosure, parameters (Information elements: IEs) may compriseone or more objects, and each of those objects may comprise one or moreother objects. For example, if parameter (IE) N comprises parameter (IE)M, and parameter (IE) M comprises parameter (IE) K, and parameter (IE) Kcomprises parameter (information element) J, then, for example, Ncomprises K, and N comprises J. In an example embodiment, when one ormore messages comprise a plurality of parameters, it implies that aparameter in the plurality of parameters is in at least one of the oneor more messages, but does not have to be in each of the one or moremessages.

Furthermore, many features presented above are described as beingoptional through the use of “may” or the use of parentheses. For thesake of brevity and legibility, the present disclosure does notexplicitly recite each and every permutation that may be obtained bychoosing from the set of optional features. However, the presentdisclosure is to be interpreted as explicitly disclosing all suchpermutations. For example, a system described as having three optionalfeatures may be embodied in seven different ways, namely with just oneof the three possible features, with any two of the three possiblefeatures or with all three of the three possible features.

Many of the elements described in the disclosed embodiments may beimplemented as modules. A module is defined here as an isolatableelement that performs a defined function and has a defined interface toother elements. The modules described in this disclosure may beimplemented in hardware, software in combination with hardware,firmware, wetware (i.e. hardware with a biological element) or acombination thereof, all of which are behaviorally equivalent. Forexample, modules may be implemented as a software routine written in acomputer language configured to be executed by a hardware machine (suchas C, C++, Fortran, Java, Basic, Matlab or the like) or amodeling/simulation program such as Simulink, Stateflow, GNU Octave, orLabVIEWMathScript. Additionally, it may be possible to implement modulesusing physical hardware that incorporates discrete or programmableanalog, digital and/or quantum hardware. Examples of programmablehardware comprise: computers, microcontrollers, microprocessors,application-specific integrated circuits (ASICs); field programmablegate arrays (FPGAs); and complex programmable logic devices (CPLDs).Computers, microcontrollers and microprocessors are programmed usinglanguages such as assembly, C, C++ or the like. FPGAs, ASICs and CPLDsare often programmed using hardware description languages (HDL) such asVHSIC hardware description language (VHDL) or Verilog that configureconnections between internal hardware modules with lesser functionalityon a programmable device. Finally, it needs to be emphasized that theabove mentioned technologies are often used in combination to achievethe result of a functional module.

The disclosure of this patent document incorporates material which issubject to copyright protection. The copyright owner has no objection tothe facsimile reproduction by anyone of the patent document or thepatent disclosure, as it appears in the Patent and Trademark Officepatent file or records, for the limited purposes required by law, butotherwise reserves all copyright rights whatsoever.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example, and notlimitation. It will be apparent to persons skilled in the relevantart(s) that various changes in form and detail can be made thereinwithout departing from the scope. In fact, after reading the abovedescription, it will be apparent to one skilled in the relevant art(s)how to implement alternative embodiments. Thus, the present embodimentsshould not be limited by any of the above described exemplaryembodiments.

In addition, it should be understood that any figures which highlightthe functionality and advantages, are presented for example purposesonly. The disclosed architecture is sufficiently flexible andconfigurable, such that it may be utilized in ways other than thatshown. For example, the actions listed in any flowchart may bere-ordered or only optionally used in some embodiments.

Further, the purpose of the Abstract of the Disclosure is to enable theU.S. Patent and Trademark Office and the public generally, andespecially the scientists, engineers and practitioners in the art whoare not familiar with patent or legal terms or phraseology, to determinequickly from a cursory inspection the nature and essence of thetechnical disclosure of the application. The Abstract of the Disclosureis not intended to be limiting as to the scope in any way.

Finally, it is the applicant's intent that only claims that include theexpress language “means for” or “step for” be interpreted under 35U.S.C. 112. Claims that do not expressly include the phrase “means for”or “step for” are not to be interpreted under 35 U.S.C. 112.

What is claimed is:
 1. A method comprising: receiving, by a wirelessdevice from a base station, configuration information for a secondarycell (SCell), the configuration information including information onresource configuration of reference signals for a channel stateinformation (CSI) reporting and information on report configuration forthe CSI reporting; receiving, by the wireless device from the basestation, a SCell activation/deactivation medium access control (MAC)control element (CE) indicating whether to activate the SCell or todeactivate the SCell; and in response to the SCellactivation/deactivation MAC CE indicating to activate the SCell,transmitting, by the wireless device to the base station, a reportincluding a layer 1 reference signal received power (RSRP) (L1-RSRP)value for the SCell and a reference signal (RS) resource indicator forthe SCell, wherein the RS resource indicator indicates a RS resourceamong a plurality of RS resources.
 2. The method of claim 1, furthercomprising: in response to the SCell activation/deactivation MAC CEindicating to deactivate the SCell, deactivating the SCell and stoppingtransmitting, by the wireless device, the report for the SCell.
 3. Themethod of claim 1, wherein, in a case that a number of reportedreference signal in the report configuration for the CSI reporting isconfigured to be larger than one, a first power value indicating thelargest measured value of reported L1-RSRP is quantized to 7-bit valuebetween −140 dbm and −44 dbm and at least one second power value of thereported L1-RSRP is quantized to a 4-bit value, indicating a power valuerelative to the first power value.
 4. The method of claim 1, whereinreference signals comprise at least one of: a first plurality of channelstate information reference signals (CSI-RSs); and a second plurality ofsynchronization signal blocks (SSBs).
 5. The method of claim 1, whereinthe transmitting comprises: transmitting, by the wireless device to thebase station, the report including the L1-RSRP value for the SCell andthe RS resource indicator for the SCell with one of a periodicreporting, an aperiodic reporting or a semi-persistent reporting.
 6. Amethod comprising: transmitting, by a base station to a wireless device,configuration information for a secondary cell (SCell), theconfiguration information including information on resourceconfiguration of reference signals for a channel state information (CSI)reporting and information on report configuration for the CSI reporting;transmitting, by the base station to the wireless device, a SCellactivation/deactivation medium access control (MAC) control element (CE)indicating whether to activate the SCell or to deactivate the SCell; andin response to the SCell activation/deactivation MAC CE indicating toactivate the SCell, receiving, by the base station from the wirelessdevice, a report including a layer 1 reference signal received power(RSRP) (L1-RSRP) value for the SCell and a reference signal (RS)resource indicator for the SCell, wherein the RS resource indicatorindicates a RS resource among a plurality of RS resources.
 7. The methodof claim 6, further comprising: transmitting, by the base station to thewireless device, configuration information including information onresource configuration of reference signals for a CSI reporting andinformation on report configuration for the CSI reporting.
 8. A wirelessdevice comprising: one or more processors; and memory storinginstructions that, when executed by the one or more processors, causethe wireless device to: receive, from a base station, configurationinformation for a secondary cell (SCell), the configuration informationincluding information on resource configuration of reference signals fora channel state information (CSI) reporting and information on reportconfiguration for the CSI reporting, receive, from the base station, aSCell activation/deactivation medium access control (MAC) controlelement (CE) indicating whether to activate the SCell or to deactivatethe SCell; and in response to the SCell activation/deactivation MAC CEindicating to activate the SCell, transmit, to the base station, areport including a layer 1 reference signal received power (RSRP)(L1-RSRP) value for the SCell and a reference signal (RS) resourceindicator for the SCell, wherein the RS resource indicator indicates aRS resource among a plurality of RS resources.
 9. The wireless device ofclaim 8, wherein the instructions, when executed by the one or moreprocessors, further cause the wireless device to: in response to theSCell activation/deactivation MAC CE indicating to deactivate the SCell,deactivate the SCell.
 10. The wireless device of claim 8, wherein, in acase that a number of reported reference signal in the reportconfiguration for the CSI reporting is configured to be larger than one,a first power value indicating the largest measured value of reportedL1-RSRP is quantized to 7-bit value between −140 dbm and −44 dbm and atleast one second power value of the reported L1-RSRP is quantized to a4-bit value, indicating a power value relative to the first power value.11. The wireless device of claim 8, wherein reference signals compriseat least one of: a first plurality of channel state informationreference signals (CSI-RS); and a second plurality of synchronizationsignal blocks (SSB).
 12. The wireless device of claim 8, wherein theinstructions, when executed by the one or more processors, further causethe wireless device to: transmit, to the base station, the reportincluding the L1-RSRP value for the SCell and the RS resource indicatorfor the SCell with one of a periodic reporting, an aperiodic reportingor a semi-persistent reporting.
 13. A base station comprising: one ormore processors; and memory storing instructions that, when executed bythe one or more processors, cause the base station to: transmit, to awireless device, configuration information for a secondary cell (SCell),the configuration information including information on resourceconfiguration of reference signals for a channel state information (CSI)reporting and information on report configuration for the CSI reporting,transmit, to the wireless device, a SCell activation/deactivation mediumaccess control (MAC) control element (CE) indicating whether to activatethe SCell or to deactivate the SCell, and in response to the SCellactivation/deactivation MAC CE indicating to activate the SCell,receive, from the wireless device, a report including a layer 1reference signal received power (RSRP) (L1-RSRP) value for the SCell anda reference signal (RS) resource indicator for the SCell, wherein the RSresource indicator indicates a RS resource among a plurality of RSresources.